Debian and all sane distros should revert this commit at once.
Changing the aesthetic of ls output is ugly, confusing, and completely
absurd. The developer who made the commit should think twice next time
before introducing such an unwanted setting and making it the default.
This is a change apprec
- Original Message -
> On 12/02/16 01:47, Jaroslav Skarvada wrote:
> > Hi,
> >
> > please revert this ugly change, it's confusing and against GNU coding
> > standards [1]:
> >
> >> Likewise, please don’t make the behavior of a command-line program depend
> >> on the type of output devic
On 12/02/16 01:47, Jaroslav Skarvada wrote:
> Hi,
>
> please revert this ugly change, it's confusing and against GNU coding
> standards [1]:
>
>> Likewise, please don’t make the behavior of a command-line program depend
>> on the type of output device it gets as standard output or standard input
Hi,
please revert this ugly change, it's confusing and against GNU coding standards
[1]:
> Likewise, please don’t make the behavior of a command-line program depend
> on the type of output device it gets as standard output or standard input.
> Device independence is an important principle of the
Hi,
Jamie Heilman wrote:
> This behavior needs to be reverted.
Definitely. Please apply kilobyte's patch, either upstream
(preferably) or at least in Debian.
> For example, consider a file who's name contains a tab, like
> "ab".
I just stumbled over a case where the quoting is even unnecessary:
On Wed, 03 Feb 2016 15:18:15 +0100 Christoph Anton Mitterer wrote:
> I think especially the "what you see [is no longer] what you get"
> point makes this feature problematic to be enabled per default (a
> problem which doesn't exist e.g. in the case of just colourisations).
That is already the cas
On Wed, Feb 03, 2016 at 03:18:15PM +0100, Christoph Anton Mitterer wrote:
Though that could be fixed... a smart quoting algorithm could produce
something like.
o\'really
or
"o'really"
That acutally exists: see --quoting-style=c
also check out --quoting-style=escape
Mike Stone
On Wed, 2016-02-03 at 04:54 +, Jamie Heilman wrote:
> Nothing about this behavior is desirable at all.
I don't think this is true either... the feature definitely has it's
point... even though I rather think it's to invasive to have it per
default.
I think especially the "what you see [is no l
Does anyone want to chime in with support for the change? I'm mostly
ambivalent, but then I don't have a lot of filenames that are actually
affected.
Mike Stone
Hi,
as this came up in #-devel, I must admit that I actually prefer the new
behaviour slightly: before "ls" used to apply a non-injective mapping
to filenames. The new transformation is at least injective, an
advantage when dealing with strange filenames in strange encodings.
For sane filenames
Re: Jamie Heilman 2016-02-02
<20160202211938.gb4...@cucamonga.audible.transient.net>
> This behavior needs to be reverted. There are too many assumptions
> being made, the quoting used is shell-specific, and not universally
> supported. For example, consider a file who's name contains a tab,
> l
Pádraig Brady wrote:
> On 02/02/16 13:19, Jamie Heilman wrote:
> > This behavior needs to be reverted. There are too many assumptions
> > being made, the quoting used is shell-specific, and not universally
> > supported. For example, consider a file who's name contains a tab,
> > like "ab".
> >
On 02/02/16 13:19, Jamie Heilman wrote:
> This behavior needs to be reverted. There are too many assumptions
> being made, the quoting used is shell-specific, and not universally
> supported. For example, consider a file who's name contains a tab,
> like "ab".
>
> $ ls
> 'a'$'\t''b'
>
> OK, so
This behavior needs to be reverted. There are too many assumptions
being made, the quoting used is shell-specific, and not universally
supported. For example, consider a file who's name contains a tab,
like "ab".
$ ls
'a'$'\t''b'
OK, so that syntax is supported by bash and zsh, so if you're usi
On Mon, 2016-02-01 at 14:52 +, Thorsten Glaser wrote:
> It’s common that new functionality is enabled by a switch,
> not by default, so you should have made -N enable this and
> keep it disabled by default to prevent very irritated reactions
> from users.
It should perhaps further be noted, tha
Pádraig Brady dixit:
>A few points about the change.
>- Users can get back to the old format by adding -N to their ls alias
But you didn’t make the -F option default either.
It’s common that new functionality is enabled by a switch,
not by default, so you should have made -N enable this and
kee
One further reason that may speak against this:
Just by looking at some ls output it's now ambiguous, whether
'foo bar'
is the quoted version of a file named “foo bar” or whether it's an
unquoted version of a file named “'foo bar'”.
As I've said, by just by looking at some output (or e.g. copy an
On Sat, 2016-01-30 at 19:03 -0800, Pádraig Brady wrote:
> ls output really isn't amenable to further processing.
> That's what find(1) is focused on.
Sure... as I've said... it's neither the best example, nor the best way
to solve the problem from that example.
But you can also consider things lik
On 30/01/16 15:45, Christoph Anton Mitterer wrote:
> Hey.
>
> I've also just stumbled over this... while the idea is nice in
> principle, I think it's quite dangerous as well... even if behaviour is
> preserved when output goes to a terminal.
>
> a) The quotation alone doesn't necessarily help wi
Hey.
I've also just stumbled over this... while the idea is nice in
principle, I think it's quite dangerous as well... even if behaviour is
preserved when output goes to a terminal.
a) The quotation alone doesn't necessarily help with copy&paste,
depending on where you paste.
b) When the pasted
On 29/01/16 16:50, Thorsten Glaser wrote:
> Package: coreutils
> Version: 8.25-1
> Severity: minor
>
> tglase@tglase-nb:~ $ mkdir -p foo/{a,b\ c}; cd foo; /bin/ls
>
> a 'b c'
>
> ’nuff said… this *should* be:
>
> (pbuild17294)root@tglase-nb:
Package: coreutils
Version: 8.25-1
Severity: minor
tglase@tglase-nb:~ $ mkdir -p foo/{a,b\ c}; cd foo; /bin/ls
a 'b c'
’nuff said… this *should* be:
(pbuild17294)root@tglase-nb:/# mkdir -p foo/{a,b\ c}; cd foo; /bin/ls
a b c
-- System In
22 matches
Mail list logo
