From: Michael Albinus <michael.albinus@gmx.de>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 64897@debbugs.gnu.org, Warren Lynn <wrn.lynn@gmail.com>
Subject: bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command
Date: Sun, 13 Aug 2023 09:42:50 +0200 [thread overview]
Message-ID: <87jztzz8ud.fsf@gmx.de> (raw)
In-Reply-To: <87wmxzr3ms.fsf@web.de> (Michael Heerdegen's message of "Sun, 13 Aug 2023 06:02:35 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
Hi Michael,
> You are correct, it seems I wasted your time: your change didn't
> introduce a regression. I'm very sorry.
No problem. My main job as Tramp maintainer is to explain other people
their configuration :-)
> Now I can't make sense of the past days. I particular I don't
> understand why I did not see the quoted file names in find-dired buffers
> until some days ago - although I used find-dired nearly daily, and
> didn't change any related settings. The problem appeared at the time of
> your patch, but now I can reproduce the same issue with older Emacs
> versions, too. I must be missing something.
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>.
> Anyway, what do you think about adding the -N switch to the `ls`
> switches to prevent the broken file lines? Do you know if it would
> introduce any problems or is not available for all `ls` versions we have
> to expect?
"-N" isn't a default ls option. It doesn't work on my QNAP NAS, for
example (being busybox ls there). See
<https://pubs.opengroup.org/onlinepubs/009696899/utilities/ls.html> for
POSIX conform ls arguments.
> Michael.
Best regards, Michael.
next prev parent reply other threads:[~2023-08-13 7:42 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 [this message]
2023-08-13 8:20 ` Eli Zaretskii
2023-08-13 9:33 ` Michael Albinus
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=87jztzz8ud.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=64897@debbugs.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).