unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 64897@debbugs.gnu.org, wrn.lynn@gmail.com
Subject: bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command
Date: Sun, 13 Aug 2023 11:33:09 +0200	[thread overview]
Message-ID: <87edk7z3qi.fsf@gmx.de> (raw)
In-Reply-To: <83fs4ncq0y.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Aug 2023 11:20:13 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

>> GNU ls has changed its default how to quote special characters in file
>> names. Likely, you've got a recent version of coreutils on your machine.
>>
>> This change has raised controversioal discussions, but now it
>> exists. See <https://www.gnu.org/software/coreutils/quotes.html>.
>
> Maybe we should invoke 'ls' via a pipe, rather than PTY, so that this
> change (which AFAIU we don't need in Dired) doesn't affect us?  Of
> course, this will probably not help remote invocations.  But maybe we
> should inject "QUOTING_STYLE=literal" into the environment in those
> cases?

I don't believe we must change anything. Calling find-name-dired from
emacs -Q, it ends up in "find . \( -name <pattern> \) -ls". This works
as expected, because the -ls argument of find is not affected by the
change in GNU ls.

The problem happens only, if people like Michael prefer to use the ls
command directly. In that case they are responsible themselves to use
proper ls arguments, matching the ls version on their system.

Best regards, Michael.





  reply	other threads:[~2023-08-13  9:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 14:24 bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command Warren Lynn
2023-07-27 15:55 ` Michael Albinus
     [not found]   ` <CAMyoMRXkC+UkeHSpA7gZdUXkHySFqjDOni6hjoUVWCWg47KVow@mail.gmail.com>
     [not found]     ` <87sf985m0m.fsf@gmx.de>
     [not found]       ` <CAMyoMRUL6nEyLa2B8rnrq_9C3jVfBRpzo_N6L433M1RHN0CB6A@mail.gmail.com>
2023-07-31 15:53         ` Michael Albinus
2023-08-05 23:35   ` Michael Heerdegen
2023-08-06 11:02     ` Michael Albinus
2023-08-07  1:17       ` Michael Heerdegen
2023-08-07  2:17         ` Michael Heerdegen
2023-08-12  3:50       ` Michael Heerdegen
2023-08-12 12:38         ` Michael Albinus
2023-08-13  4:02           ` Michael Heerdegen
2023-08-13  7:42             ` Michael Albinus
2023-08-13  8:20               ` Eli Zaretskii
2023-08-13  9:33                 ` Michael Albinus [this message]
2023-08-13  9:46                   ` Eli Zaretskii
2023-08-13 10:01                     ` Michael Albinus
2023-08-14  1:25                     ` Michael Heerdegen
2023-08-14 11:52                       ` Eli Zaretskii
2023-08-15  3:15                         ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87edk7z3qi.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=64897@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=wrn.lynn@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).