> I could imagine that, but the columns aren't in a fixed place if the number
> of blocks or inodes is greater than a particular value, wouldn't this break
> those scripts already?
On very few machines with long paths, and where people do such foolish
system-dependent parsing operations.
However your diff changes it on *all machines*.
> And if you meant comparing the header as a string, then the first column
> isn't fixed either, it depends on the length of the longest disk path:
> (void)printf("%-*.*s %s Used Avail Capacity",
> maxwidth, maxwidth, "Filesystem", header);
Perhaps...
> I wanted to make similar changes to ps(1), the TIME and VSZ/RSS columns
> can misalign the table. I suppose the same argument can be made against
> that change.
Ugh, before the days of pkill/pgrep, that would have been even more
implausible.
Variable-width sizing is a horrific thing on 80-column screens, I'd say it
has been avoided in commonly run commands.
