Consider this usage of rs(1):
rs -n -z -c, <<CSV
a,b,c
dd,ee,ff
CSV
The above snippet emits:
a b c dd ee ff
But I was expecting to see something like this:
a b c
dd ee ff
The manual suggests that the output array shape should match the input array shape unless configured otherwise.
rs -h using the same input emits 2 3, which suggests that rs does correctly identify the input array shape.
What am I misunderstanding in the usage of rs? Is there a way to have it automatically format the output with the same shape as the input?
-T(pure transpose) then piping the result through a secondrs -Tseems to work for me – steeldriver Jan 31 '23 at 22:09rsquestion butcolumn -s, -t <<CSV ...does what you want. – glenn jackman Feb 01 '23 at 03:00columnwhen a leading cell is "blank", which is how I foundrsin the first place! I made a follow-up question about it: https://unix.stackexchange.com/q/733969/73256 – shadowtalker Feb 01 '23 at 16:27rshas the same problem ascolumnin that example! It's a little surprising that these basic tools behave so weirdly. I'm tempted to write my own AWK script and ignore all these. – shadowtalker Feb 01 '23 at 16:27rsis used to reshape data. It seems that you don't actually want to reshape the data, which in turn meansrsmight be the wrong tool for the job. – Kusalananda Feb 13 '23 at 12:10rowsandcolsis the-Toption, which transposes the input. All other options rely on the user specifying eitherrowsorcolsexplicitly to reshape the data to that specification. – Kusalananda Feb 14 '23 at 17:32