User talk:Aks: Difference between revisions

From Rosetta Code
Content added Content deleted
 
(5 intermediate revisions by 3 users not shown)
Line 7: Line 7:
::P.S: I searched for a section of the man page text and came up with links like [http://www.gsp.com/cgi-bin/man.cgi?section=1&topic=rs this] and [http://www.unix.com/man-page/OSX/1/RS/ this]. Now I have the links, it would be OK to remove the actual man page from your talk page if it is cluttering. Thanks again - I didn't know about rs for reshape. --[[User:Paddy3118|Paddy3118]] 04:43, 8 February 2010 (UTC)
::P.S: I searched for a section of the man page text and came up with links like [http://www.gsp.com/cgi-bin/man.cgi?section=1&topic=rs this] and [http://www.unix.com/man-page/OSX/1/RS/ this]. Now I have the links, it would be OK to remove the actual man page from your talk page if it is cluttering. Thanks again - I didn't know about rs for reshape. --[[User:Paddy3118|Paddy3118]] 04:43, 8 February 2010 (UTC)


==rs man page==
== Machinations behind the user page ==
<lang Unix Shell>
$ man rs | cat
RS(1) RS(1)


When you use the mylang template, the text you use to identify the language automatically puts your username as part of a MediaWiki category. Unfortunately, MediaWiki doesn't have a mechanism for aliasing categories, so I can't tell it "hey, PL/I and PL/1 are the same thing". As a result, if you have PL/I in the mylang template, you wind up in [[:Category:PL/I User]], whereas if you have PL/1 in the mylang template, you wind up in [[:Category:PL/1 User]]. It's a rather annoying software limitation that won't be fixed until someone has time to write a patch. I understand your frustrations. --[[User:Short Circuit|Michael Mol]] 20:19, 17 February 2010 (UTC)

: In any case, we are following the naming conventions used by Wikipedia. See [[wp:PL/I]]. --[[User:IanOsgood|IanOsgood]] 22:20, 17 February 2010 (UTC)

This makes perfect sense -- having an automaton tracking down language references. Thanks for the explanation. --[[User:Aks|Aks]] 21:01, 19 February 2010 (UTC)
NAME
rs - reshape a data array

SYNOPSIS
rs [ -[csCS][x][kKgGw][N]tTeEnyjhHm ] [ rows [ cols ] ]

DESCRIPTION
Rs reads the standard input, interpreting each line as a row of blank-
separated entries in an array, transforms the array according to the
options, and writes it on the standard output. With no arguments it
transforms stream input into a columnar format convenient for terminal
viewing.

The shape of the input array is deduced from the number of lines and
the number of columns on the first line. If that shape is inconve-
nient, a more useful one might be obtained by skipping some of the
input with the -k option. Other options control interpretation of the
input columns.

The shape of the output array is influenced by the rows and cols speci-
fications, which should be positive integers. If only one of them is a
positive integer, rs computes a value for the other which will accommo-
date all of the data. When necessary, missing data are supplied in a
manner specified by the options and surplus data are deleted. There
are options to control presentation of the output columns, including
transposition of the rows and columns.

The options are described below.

-cx Input columns are delimited by the single character x. A miss-
ing x is taken to be `^I'.

-sx Like -c, but maximal strings of x are delimiters.

-Cx Output columns are delimited by the single character x. A miss-
ing x is taken to be `^I'.

-Sx Like -C, but padded strings of x are delimiters.

-t Fill in the rows of the output array using the columns of the
input array, that is, transpose the input while honoring any
rows and cols specifications.

-T Print the pure transpose of the input, ignoring any rows or cols
specification.

-kN Ignore the first N lines of input.

-KN Like -k, but print the ignored lines.

-gN The gutter width (inter-column space), normally 2, is taken to
be N.

-GN The gutter width has N percent of the maximum column width added
to it.

-e Consider each line of input as an array entry.

-n On lines having fewer entries than the first line, use null
entries to pad out the line. Normally, missing entries are
taken from the next line of input.

-y If there are too few entries to make up the output dimensions,
pad the output by recycling the input from the beginning. Nor-
mally, the output is padded with blanks.

-h Print the shape of the input array and do nothing else. The
shape is just the number of lines and the number of entries on
the first line.

-H Like -h, but also print the length of each line.

-j Right adjust entries within columns.

-wN The width of the display, normally 80, is taken to be the posi-
tive integer N.

-m Do not trim excess delimiters from the ends of the output array.

-z Adapt column widths to fit the largest entries appearing in
them.

With no arguments, rs transposes its input, and assumes one array entry
per input line unless the first non-ignored line is longer than the
display width. Option letters which take numerical arguments interpret
a missing number as zero unless otherwise indicated.

EXAMPLES
Rs can be used as a filter to convert the stream output of certain pro-
grams (e.g., spell, du, file, look, nm, who, and wc(1)) into a conve-
nient ``window'' format, as in

who | rs

This function has been incorporated into the ls(1) program, though for
most programs with similar output rs suffices.

To convert stream input into vector output and back again, use

rs 1 0 | rs 0 1

A 10 by 10 array of random numbers from 1 to 100 and its transpose can
be generated with

jot -r 100 | rs 10 10 | tee array | rs
-T > tarray

In the editor vi(1), a file consisting of a multi-line vector with 9
elements per line can undergo insertions and deletions, and then be
neatly reshaped into 9 columns with

:1,$!rs 0 9

Finally, to sort a database by the first line of each 4-line field, try

rs -eC 0 4 | sort | rs -c 0 1


AUTHOR
John A. Kunze <jak@ucop.edu>

SEE ALSO
jot(1), vi(1), sort(1), pr(1)

BUGS
Handles only two dimensional arrays.

The algorithm currently reads the whole file into memory, so files that
do not fit in memory will not be reshaped.

Fields cannot be defined yet on character positions.

Re-ordering of columns is not yet possible.

There are too many options.



4th Berkeley Distribution December 30, 1993 RS(1)
</lang>

==rs command info==
<lang Unix Shell>
$ which rs
/usr/bin/rs
aks@stocks:fundAnalysis 19:14:19 (0) <1592>
$ ls -l /usr/bin/rs
-r-xr-xr-x 1 root wheel 18156 Mar 20 2005 /usr/bin/rs*
</lang>

Latest revision as of 21:01, 19 February 2010

Welcome to Rosetta Code! (And nice use of the mylang template, BTW...) You can visit my userpage to see who I am, but I'm not particularly visible these days; Most of my involvement is now related to the underlying server and software. I notice you're familiar with PDP and UNIVAC assembler. I haven't learned much about these; I'd love to see how their ISAs and VMs relate to more recent and familiar ones, but I don't think we yet have many tasks suitable for such comparisons. --Michael Mol 09:15, 15 September 2009 (UTC)

rs Unix command?

Hi. Could you tell me where I could find info on the rs Unix command used in the column aligner task? Is it a standard Unix command? Thanks. --Paddy3118 23:43, 7 February 2010 (UTC)

Thanks. That's great. I didn't know the rs command, and my previous googling returned nothing, as well as rs not being found on my Cygwin Unix emulation installation.
P.S: I searched for a section of the man page text and came up with links like this and this. Now I have the links, it would be OK to remove the actual man page from your talk page if it is cluttering. Thanks again - I didn't know about rs for reshape. --Paddy3118 04:43, 8 February 2010 (UTC)

Machinations behind the user page

When you use the mylang template, the text you use to identify the language automatically puts your username as part of a MediaWiki category. Unfortunately, MediaWiki doesn't have a mechanism for aliasing categories, so I can't tell it "hey, PL/I and PL/1 are the same thing". As a result, if you have PL/I in the mylang template, you wind up in Category:PL/I User, whereas if you have PL/1 in the mylang template, you wind up in Category:PL/1 User. It's a rather annoying software limitation that won't be fixed until someone has time to write a patch. I understand your frustrations. --Michael Mol 20:19, 17 February 2010 (UTC)

In any case, we are following the naming conventions used by Wikipedia. See wp:PL/I. --IanOsgood 22:20, 17 February 2010 (UTC)

This makes perfect sense -- having an automaton tracking down language references. Thanks for the explanation. --Aks 21:01, 19 February 2010 (UTC)