Re: broken ls in coreutils 8.25

2016-02-02 Thread Harald Dunkel
-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. > > Ye

broken ls in coreutils 8.25

2016-01-31 Thread Harald Dunkel
-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.

"full" man pages, please?

2017-03-21 Thread Harald Dunkel
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

suggestion for a new recursive directory ls

2017-08-31 Thread Harald Dunkel
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

is there a real escape "quoting" style for ls?

2018-05-13 Thread Harald Dunkel
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

Re: is there a real escape "quoting" style for ls?

2018-05-13 Thread Harald Dunkel
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

Re: ls is broken, what's next cd?

2018-02-12 Thread Harald Dunkel
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

Re: ls is broken, what's next cd?

2018-02-16 Thread Harald Dunkel
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

suggestion: $LS_ARGS

2018-02-23 Thread Harald Dunkel
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

Re: suggestion: $LS_ARGS

2018-02-26 Thread Harald Dunkel
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.

/bin/echo -- $var

2019-08-14 Thread Harald Dunkel
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

Re: /bin/echo -- $var

2019-08-15 Thread Harald Dunkel
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 "-n"

Re: /bin/echo -- $var

2019-08-15 Thread Harald Dunkel
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

bug#8081: sort -z and shuf -z don't work

2011-02-19 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: coreutils Version: 8.10 Hi folks, According to the man page sort -z and shuf -z are supposed to end lines with 0 byte, not newline. This doesn't work. Example: % ( echo 1; echo 2; echo 3 ) | tac | sort -z | xargs -0 -L 1 echo xxx xxx 3 2

bug#20143: --dry-run for chmod and chown

2015-03-19 Thread Harald Dunkel
Hi folks, a dry run mode for chmod and chown would be very helpful, especially together with -v --reference-file. Hopefully I am not too blind to see. Most recent version I checked was coreutils 8.23. Thanx very much. Please keep on your good work Harri -- aixigo AG, Karl-Friedrich-Strasse