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

[Andreas Schwab]

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

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."