Bug#886173: general: ls quotes results with special characters in its output

Hello, On Tue, Jan 02 2018, Ben Hutchings wrote: > The output of ls on a terminal has never, in general, been an accurate > reflection of the contents of a directory. Consider that filenames > can contain *any* byte value other than '\0' or '/', so including > carriage return, newline,

Bug#886173: general: ls quotes results with special characters in its output

mqu...@neosmart.net writes: > In particular, `ls` output (both in regular and `-l` modes) wraps in > single quotes the names of files that contain special characters (or, at > least, a parenthesis), meaning its output is not an accurate reflection > of the actual contents of the directory. This

Bug#886173: general: ls quotes results with special characters in its output

On Tue, Jan 2, 2018 at 3:26 PM, Ben Hutchings wrote: > The output of ls on a terminal has never, in general, been an accurate > reflection of the contents of a directory. Consider that filenames can > contain *any* byte value other than '\0' or '/', so including carriage >

Bug#886173: general: ls quotes results with special characters in its output

Control: reassign -1 coreutils On Tue, 2018-01-02 at 20:38 +, mqu...@neosmart.net wrote: [...] > In particular, `ls` output (both in regular and `-l` modes) wraps in > single quotes the names of files that contain special characters (or, at > least, a parenthesis), meaning its output is not

Bug#886173: general: ls quotes results with special characters in its output

Package: general Severity: normal Dear Maintainer, On a clean installation of debian buster, I ran into an issue where the output of `ls` in various modes led me to confusedly attempt to figure out where my scripting had gone wrong. In particular, `ls` output (both in regular and `-l` modes)