From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54636@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#54636: dired fails to update subdirs when files are created/deleted/renamed
Date: Wed, 30 Mar 2022 18:47:49 +0200 (GMT+02:00) [thread overview]
Message-ID: <8369e675-2d82-42aa-9b13-29524c6a4ac6@gnu.org> (raw)
In-Reply-To: <83wngb75o5.fsf@gnu.org>
30.03.2022 18:42:48 Eli Zaretskii <eliz@gnu.org>:
>> From: Tassilo Horn <tsdh@gnu.org>
>> Cc: schwab@linux-m68k.org, 54636@debbugs.gnu.org
>> Date: Wed, 30 Mar 2022 18:29:29 +0200
>>
>>> I'll prepare a patch in that direction later.
>>
>> Here it is:
>> [...]
>> I think that's a better approach than changing dired-buffers-for-dir
>> which I shouldn't have done in the first place.
>
> If so, can we restore dired-buffers-for-dir to what it was in Emacs
> 27? AFAICT, the only difference now is that you use 'when' instead of
> just 'and' -- is there a reason for that?
No reason except stylistic preference.
I can change that if you want.
Bye,
Tassilo
next prev parent reply other threads:[~2022-03-30 16:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 11:15 bug#54636: dired fails to update subdirs when files are created/deleted/renamed Andreas Schwab
2022-03-30 12:03 ` Eli Zaretskii
2022-03-30 12:11 ` Andreas Schwab
2022-03-30 12:43 ` Tassilo Horn
2022-03-30 13:22 ` Eli Zaretskii
2022-03-30 13:29 ` Tassilo Horn
2022-03-30 13:56 ` Eli Zaretskii
2022-03-30 14:30 ` Tassilo Horn
2022-03-30 15:51 ` Eli Zaretskii
2022-03-30 16:02 ` Tassilo Horn
2022-03-30 16:29 ` Tassilo Horn
2022-03-30 16:42 ` Eli Zaretskii
2022-03-30 16:47 ` Tassilo Horn [this message]
2022-03-30 16:55 ` Eli Zaretskii
2022-03-30 17:51 ` Tassilo Horn
2022-04-05 11:30 ` Eli Zaretskii
2022-03-30 16:30 ` Eli Zaretskii
2022-03-30 16:32 ` Tassilo Horn
2023-07-08 18:31 ` Jakub Ječmínek
2023-07-09 11:09 ` Eli Zaretskii
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=8369e675-2d82-42aa-9b13-29524c6a4ac6@gnu.org \
--to=tsdh@gnu.org \
--cc=54636@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.org \
/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.