procps/ps
Craig Small b2f49b105d Closes: #9 ps: Remove Unix98 output limitations
ps previously followed the Unix98 standard when it comes to
user-defined output, sometimes. This meant you could have
user output format with a header that included commas and
equals signs. It was dependent on if ps thought you wanted
sysv or bsd format and THAT was dependent on things in previous
options.

It was very confusing to a user because
 ps p $$ -o pid=,comm=
gave you a two-column output but
 ps -p $$ -o pid=,comm=
would give you a one column output with the header ",comm="

The -p versus p means (to ps) you want sysv or bsd parsing.
Unix98 standard or not, this is plainly just silly.

The commit removes any of the quirks Unix98 has with user defined
output.  If you really wanted a ps header with commas in the output,
today isn't your day.

Signed-off-by: Craig Small <csmall@enc.com.au>
2015-10-26 11:18:52 +11:00
..
common.h Closes: #9 ps: Remove Unix98 output limitations 2015-10-26 11:18:52 +11:00
COPYING
display.c ps: exploit the simplified library interface for wchan 2015-06-19 19:09:20 +10:00
global.c Closes: #9 ps: Remove Unix98 output limitations 2015-10-26 11:18:52 +11:00
HACKING
help.c ps: add -q/q/--quick-pid option 2014-07-10 21:24:19 +02:00
output.c ps: display control group name 2015-08-15 17:10:38 +10:00
parser.c Closes: #9 ps: Remove Unix98 output limitations 2015-10-26 11:18:52 +11:00
ps.1 ps: display control group name 2015-08-15 17:10:38 +10:00
regression procps 010114 2002-02-01 22:47:29 +00:00
select.c ps: add -q/q/--quick-pid option 2014-07-10 21:24:19 +02:00
sortformat.c Closes: #9 ps: Remove Unix98 output limitations 2015-10-26 11:18:52 +11:00
stacktrace.c ps: cut out code unused code 2012-11-06 22:30:02 +11:00