One idea not addressed in #17 was that the truncation of the cmdline contents in the COMMAND column of zps's output maybe should be adapted to allow longer output depending on the number of available terminal columns. An example of this would be ps, which attempts to display the contents up to the line limit of the interactive terminal, unless stdout is piped to a different program's stdin – like grep, for example –, in which case the whole cmdline is displayed.
Introducing this functionality would still have one issue, however: Users looking for a specific substring in the interactive output of zps would not find every match that grep-ing would show, due to differences in the maximum line lengths and occurring truncation.
Thus, it might actually be desirable to actually limit the lengths in any case, so users are required to check the contents through alternative sources/programs.
One idea not addressed in #17 was that the truncation of the
cmdlinecontents in theCOMMANDcolumn ofzps's output maybe should be adapted to allow longer output depending on the number of available terminal columns. An example of this would beps, which attempts to display the contents up to the line limit of the interactive terminal, unlessstdoutis piped to a different program'sstdin– likegrep, for example –, in which case the wholecmdlineis displayed.Introducing this functionality would still have one issue, however: Users looking for a specific substring in the interactive output of
zpswould not find every match thatgrep-ing would show, due to differences in the maximum line lengths and occurring truncation.Thus, it might actually be desirable to actually limit the lengths in any case, so users are required to check the contents through alternative sources/programs.