On 8/14/19 3:10 PM, Eric Blake wrote:
On 8/14/19 7:01 AM, Harald Dunkel wrote:
Shouldn't it be just
-n
No, because 'echo' is one of the few exceptions to the rule, in that
POSIX specifically mandates that it NOT recognize -- as an
end-of-options marker.
But then the
On 8/14/19 10:23 PM, Stephane Chazelas wrote:
2019-08-14 09:28:22 -0700, Kaz Kylheku (Coreutils):
[...]
According to POSIX, echo doesn't take options. It is specified
that "Implementations shall not support any options."
(We have options, though, so things are complicated.)
[...]
The POSIX sp
Hi folks,
I just learned by accident that
var="-n"
/bin/echo -- $var
actually prints
-- -n
Shouldn't it be just
-n
?
Other tools in coreutils use '--' to indicate "stop parsing for
command line flags", e.g. touch, ls and rm:
% /bin/touch -- -l
On 5/13/18 1:08 PM, L A Walsh wrote:
>
> If you look under --quoting-style, you'll
> see:
> --quoting-style=WORD use quoting style WORD for entry names:
> literal, locale, shell, shell-always,
> shell-escape, shell-escape-always, c, escape
>
> I
Hi folks,
How can I tell ls to create a *real* escape shell style without quotes?
A file name like
A Knight's Tale: Part 2
should be shown as
A\ Knight\'s\ Tale\:\ Part\ 2
Similar to bash's command line completion.
I had hoped for QUOTING_STYLE=escape, but it just gives me
Hi Eric,
On 02/23/18 15:01, Eric Blake wrote:
On 02/23/2018 02:14 AM, Harald Dunkel wrote:
Hi folks,
I would like to suggest to introduce an environment variable
"LS_ARGS", holding the default arguments to ls (similar to $LESS).
This could help to simplify the user environment.
Hi folks,
I would like to suggest to introduce an environment variable
"LS_ARGS", holding the default arguments to ls (similar to $LESS).
This could help to simplify the user environment. You don't have
to create clumsy aliases for ls anymore, but you could set
export LS_ARGS="--color=n
Hi Ben,
On 02/15/18 08:16, Bernhard Voelker wrote:
I'm not sure what's happening there, but it seems that your terminal
doesn't know how to display the 2-byte representation "c3 a4"; neither
gnome-terminal nor xterm have problems to display it here:
$ /bin/ls -log /tmp/Q*
-rw-r--r-- 1 0
Hi Berny,
On 02/08/18 00:34, Bernhard Voelker wrote:
On 02/07/2018 10:12 AM, Harald Dunkel wrote:
I wonder who is supposed to benefit from this change? For a
human eye these constructs are simply unrecognizable, unless
you look*very* closely.
:
:
This is nice IMO.
Your example was quite
On 02/05/18 20:27, Bernhard Voelker wrote:
On 02/05/2018 07:45 PM, Kaz Kylheku (Coreutils) wrote:
> There is no need for this pointless garbage. Unix has gotten along
> without quoting the output of ls for 43 years now.
If you search the mailing list archive, then you'll see that
this has alre
Hi Pádraig,
I highly appreciate your clever optimizations, but as written
before, I am looking for a new feature in /bin/ls. A recursion
is already in. ls produces just a weird output, so I would assume
this new feature is easy to implement.
Harri
Hi folks,
One of my favorites is
ls -ld `find /some/dir -print`
It creates a much better readable output than "ls -R".
Its shortcomings are clear: 2 many arguments on the command
line, takes an awful lot of time to execute, problems with
space chars, etc. Surely this command line could
Hi folks,
I highly appreciate your work to provide excellent tools for
decades.
There is one thing I would like to ask for, though: Would you
mind to support "full" man pages instead of the "full-docu-can-
be-found-in-info-or-on-the-web-only" pages (e.g. dd(1), cpio(1))?
Advantages:
- no brea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/16 14:30, Eric Blake wrote:
> On 02/01/2016 11:17 PM, Harald Dunkel wrote:
>>
>> This means that the user has to count '\' and "'" in the output of ls to get
>> the "real" filename
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Pádraig,
On 02/01/16 17:07, Pádraig Brady wrote:
> On 31/01/16 06:48, Harald Dunkel wrote:
>
> The reasons we changed the default was:
>
> - It only happens when outputting to terminals
This means if you use "ls -1 | so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi folks,
how comes that suddenly I have to define an environment variable
QUOTING_STYLE=literal
for something that worked very well since the 70s? I appreciate
your continuous effort to improve coreutils, but this change is a
bad move.
16 matches
Mail list logo