bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Eric Blake
On 05/02/2016 03:27 AM, Michael Albinus wrote: > Hi, > > I have a file called "foobar". Yes, it includes the char in > its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . That is intentional; in the same vein as the way 'ls' changed its default output for files with awkward characters.

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Michael Albinus
Pádraig Brady writes: Hi, >> I have a file called "foobar". Yes, it includes the char in >> its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . > >> This looks pretty strange. It is with "stat (GNU coreutils) 8.25". Earlier >> stat versions, say "stat (GNU

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Pádraig Brady
On 02/05/16 15:27, Michael Albinus wrote: Eric Blake writes: Hi Eric, I have a file called "foobar". Yes, it includes the char in its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . That is intentional; in the same vein as the way 'ls' changed its default output

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Michael Albinus
Pádraig Brady writes: >> Thanks for the hint with QUOTING_STYLE. However, it doesn't work for me: >> >> # env QUOTING_STYLE=escape /usr/bin/stat -c %N /tmp/foo* >> '/tmp/foo'$'\t''bar' > > Right, stat currently hard codes the "shell" style. > It probably makes sense to have

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Pádraig Brady
On 02/05/16 10:27, Michael Albinus wrote: Hi, I have a file called "foobar". Yes, it includes the char in its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . This looks pretty strange. It is with "stat (GNU coreutils) 8.25". Earlier stat versions, say "stat (GNU coreutils) 6.12" on

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Paul Eggert
On 05/02/2016 03:19 PM, Ruediger Meier wrote: This new quoting style default is just ugly, unreadable and annoying. If you can think of an unambiguous output style that is beautiful, readable, and pleasant, please let us know.

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Ruediger Meier
On Monday 02 May 2016, Michael Albinus wrote: > Pádraig Brady writes: > > Hi, > > >> I have a file called "foobar". Yes, it includes the > >> char in its name. When I call "stat -c %N", I get 'foo'$'\t''bar' > >> . > >> > >> This looks pretty strange. It is with "stat (GNU

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Michael Albinus
Eric Blake writes: Hi Eric, >> I have a file called "foobar". Yes, it includes the char in >> its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . > > That is intentional; in the same vein as the way 'ls' changed its > default output for files with awkward characters.

bug#23422: stat -c %N returns strange results for file names including

2016-05-02 Thread Michael Albinus
Hi, I have a file called "foobar". Yes, it includes the char in its name. When I call "stat -c %N", I get 'foo'$'\t''bar' . This looks pretty strange. It is with "stat (GNU coreutils) 8.25". Earlier stat versions, say "stat (GNU coreutils) 6.12" on a very old machine I have access too, used to