From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>,
64897@debbugs.gnu.org, wrn.lynn@gmail.com
Subject: bug#64897: 29.0.91; Bug (and patch) in find-dired-with-command
Date: Mon, 14 Aug 2023 03:25:57 +0200 [thread overview]
Message-ID: <87cyzql8ii.fsf@web.de> (raw)
In-Reply-To: <83edk7cm10.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Aug 2023 12:46:35 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I was thinking about Dired, not about find-name-dired.
>
> Are you saying that Dired is not affected by this change in Coreutils'
> behavior?
If you look in `dired-insert-directory': this is already handled for
Dired in a careful way. As requested in Bug#63142, fixed by a certain
Eli Z in May :-)
Should we do the same for find-dired?
Michael.
next prev parent reply other threads:[~2023-08-14 1:25 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
2023-08-13 9:46 ` Eli Zaretskii
2023-08-13 10:01 ` Michael Albinus
2023-08-14 1:25 ` Michael Heerdegen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyzql8ii.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=64897@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.