> > impacts what data the user can see. (That is, the IPMPSTAT_NCOL check in > > ipmpstat.c is just a subtle way of determining what fields should be > > displayed by "all" and the ones that should be displayed by default. Its > > results are always the same, regardless of screen width.) > > > > Agree with the change in behavior that you flag, but then I am > puzzled about the IPMPSTAT_NCOL constraint itself. If I do "ipmpstat -pn" > with the onnv version of ipmpstat, it truncates out the RTTDEV because > the output goes over 80 columns. When I read this code, I assumed > that the "80" came from the default 80x25 xterm size. But if the > xterm is less than 80 columns, and "-o" is not specified, don't we > want the code to recognize the new constraint correctly (otherwise > the 80 looks a bit arbitrary)?
As above, this was done to ensure that the output was deterministic. I felt that using the screen width to determine what data can be shown is too subtle and would lead people generally being confused about what is actually shown by default. Since 80 columns generally considered the standard line width, if no output fields are specified, it always displays the fields that will fit within 80 columns. Obviously, if specific fields are given, then those fields are always output regardless of the screen width. -- meem
