bug#10915: 8.13: df -- overly long output lines are very hard to read

2012-07-27 Thread Bernhard Voelker
On 07/26/2012 06:11 PM, Pádraig Brady wrote: > On 07/26/2012 04:43 PM, Bernhard Voelker wrote: >> On 07/26/2012 04:23 PM, Pádraig Brady wrote: >>> So a full --output list supported by df could be >>> FSTYPE,SOURCE,TARGET,SIZE,USED,AVAIL,FREEPCT Today, there's no FREEPCT, but USEDPCT. I'd leave th

bug#10915: 8.13: df -- overly long output lines are very hard to read

2012-07-27 Thread Pádraig Brady
On 07/27/2012 08:00 AM, Bernhard Voelker wrote: > On 07/26/2012 06:11 PM, Pádraig Brady wrote: >> On 07/26/2012 04:43 PM, Bernhard Voelker wrote: >>> On 07/26/2012 04:23 PM, Pádraig Brady wrote: > So a full --output list supported by df could be FSTYPE,SOURCE,TARGET,SIZE,USED,AVAIL,FREEP

bug#10915: 8.13: df -- overly long output lines are very hard to read

2012-07-27 Thread Jim Meyering
Pádraig Brady wrote: ... >> df --printf="%U\0%s\0%m\0\n" >> >> As already said, this would be a greater change in df.c, >> but some code could surely be shared with stat.c and maybe >> in future with "ls --format=..." ;-) >> >> I'm not against --output, but the advantage of a more >> flexible --p

bug#10915: 8.13: df -- overly long output lines are very hard to read

2012-07-27 Thread Bernhard Voelker
On 07/27/2012 02:04 PM, Jim Meyering wrote: > However, it is hard to judge without seeing the actual changes. > If you feel strongly about it, go ahead and implement your preference. > Maybe the resulting code will be small and clean enough that the added > flexibility will be an obvious net gain.