bug#25495: WTF? Chmod (and presumably other coreutils) corrupt their own error messages with "smart" quotes...

2017-01-20 Thread Paul Eggert
Alain Knaff wrote: $ LC_ALL=C.UTF-8 chmod 0 chmod: cannot access ‘’: No such file or directory It looks like you're using an old version of coreutils. The current version outputs ASCII apostrophes there. This was a change committed on 2015-11-04 and released in coreutils 8.25; it mak

bug#25495: WTF? Chmod (and presumably other coreutils) corrupt their own error messages with "smart" quotes...

2017-01-20 Thread Alain Knaff
On 01/20/2017 23:33, Eric Blake wrote: > On 01/20/2017 03:44 PM, Alain Knaff wrote: >> Hi, >> >> Recently, while browsing error mails of some cron jobs, I noticed that >> chmod puts "smart" quotes into its error messages. >> >> IMHO, such gimmicks should have no place in core utilities. >> >> At

bug#25495: WTF? Chmod (and presumably other coreutils) corrupt their own error messages with "smart" quotes...

2017-01-20 Thread Eric Blake
On 01/20/2017 03:44 PM, Alain Knaff wrote: > Hi, > > Recently, while browsing error mails of some cron jobs, I noticed that > chmod puts "smart" quotes into its error messages. > > IMHO, such gimmicks should have no place in core utilities. > > At least this behavior should be optional via confi

bug#25495: WTF? Chmod (and presumably other coreutils) corrupt their own error messages with "smart" quotes...

2017-01-20 Thread Alain Knaff
Hi, Recently, while browsing error mails of some cron jobs, I noticed that chmod puts "smart" quotes into its error messages. IMHO, such gimmicks should have no place in core utilities. At least this behavior should be optional via configuration or environment setting (preferably off by default)