Re: du: POSIX mandating a single space instead of tab?

[Bernhard Voelker]

On 04/28/2015 09:44 AM, Andreas Schwab wrote:
> Bernhard Voelker
> <address@hidden> writes:
>
> > Reading POSIX [0] again because of bug#20442 [1], I think that
> > GNU du is violating the spec:
> >
> >      The output from du shall consist of the amount of space allocated
> >      to a file and the name of the file, in the following format:
> >
> >      "%d %s\n", <size>, <pathname>
> >
> > Instead, GNU du uses "%d\t%s\n", i.e., a tab character as delimiter,
> > even if POSIXLY_CORRECT is set.
> >
> > Do I read POSIX right?
>
> No, the space stands for any (positive) amount of white space.
>
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap05.html#tag_05

Great, even better. Thanks for the pointer.

Have a nice day,
Berny