bug#11922: df doesn't handle \n in mount entries appropriately

[Pádraig Brady]

On 07/12/2012 04:14 PM, Paul Eggert wrote:
> On 07/12/2012 04:50 AM, Pádraig Brady wrote:
>> So how about we just change \n -> \012.
> 
> That would mean we also need to change \ -> \\
> (otherwise the output would be ambiguous),
> and at that point it might make sense to escape
> space and tab consistently with the the lower
> level interface.

Right that would be the most consistent and general.
I detailed in the previous mail why I was wary.

It would change the output for df etc. in possibly more
common cases of space and tab used in names.
Maybe that case is uncommon enough to not worry about, but...

more problematically it would change the output from
the lib, so that whereas before any program could unambiguously
access the returned entries directly, now they'd have
to unescape.

seems a bit dangerous to me.

cheers,
Pádraig.