public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: strange behaviour of 'ls'
Date: Fri, 08 Apr 2016 20:36:00 -0000	[thread overview]
Message-ID: <57081627.4030508@redhat.com> (raw)
In-Reply-To: <871t6gx7ae.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On 04/08/2016 12:52 PM, Achim Gratz wrote:
> Thomas Wolff writes:
>> Like for grep which now barfs out when a character isn’t recognized in
>> the current encoding (and grep doesn’t even provide an environment
>> variable to override this mis-feature), these assumedly-modern
>> upstream changes are a nuisance.
> 
> You are barking up the wrng tree, please take that upstream.
> 
>> For ls at least, it can be fixed with the environment variable
>> QUOTING_STYLE but that isn’t even mentioned in the manual page!%§↯
>> – Poor old Unix tradition fades away.
>>
>> What about adding
>> export QUOTING_STYLE=literal
>> to /etc/profile as a fix?
> 
> No, but you're free to do whatever you wish in /etc/profile.d (or lobby
> the coreutils maintiner to provide it with the package, although I'd
> suggest that it shouldn't get installed by default).

If upstream makes it easy to install such an example profile, I'll
likewise make it easy to install in cygwin. Otherwise, I don't see any
reason to go out of my way to make cygwin diverge from upstream.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-04-08 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  7:27 Simon Bradley
2016-04-07  8:46 ` Achim Gratz
2016-04-07 11:12 ` Andrew Schulman
2016-04-08  9:50   ` Thomas Wolff
2016-04-08 18:52     ` Achim Gratz
2016-04-08 20:36       ` Eric Blake [this message]
2016-04-08 21:22       ` Thomas Wolff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57081627.4030508@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).