From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: dired cons bug?
Date: Fri, 12 Aug 2022 08:50:12 +0300 [thread overview]
Message-ID: <83r11mnh7v.fsf@gnu.org> (raw)
In-Reply-To: <35b2cf5e-a1ef-109f-0eba-4f8e30655813@gmx.at> (message from Harald Judt on Thu, 11 Aug 2022 11:23:52 +0200)
> Date: Thu, 11 Aug 2022 11:23:52 +0200
> From: Harald Judt <h.judt@gmx.at>
>
> I have found an explanation for my own question: The problem is that after a
> dired-do-xxxx command, the buffer of the _target_ directory will be refreshed.
> But the target directory of /home/user/tmp/test/a/a would be
> /home/user/tmp/test/a/, and that is different from the one used in the base
> dir of the cons (/home/user/). In fact, if I add a file /home/user/x and add
> that to the file list and delete it, the buffer will be reverted correctly. If
> I delete any of the other files, it won't.
>
> Now, what could I do to programmatically revert the current dired buffer after
> executing a dired-do command?
I have posted a patch that's supposed to fix this. Please try it.
next prev parent reply other threads:[~2022-08-12 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:26 dired cons bug? Harald Judt
2022-08-11 5:55 ` Jean Louis
2022-08-11 6:42 ` Eli Zaretskii
2022-08-11 9:32 ` Jean Louis
2022-08-11 8:11 ` Harald Judt
2022-08-11 9:23 ` Harald Judt
2022-08-12 5:50 ` Eli Zaretskii [this message]
2022-08-11 13:30 ` Eli Zaretskii
2022-08-11 13:38 ` [External] : " Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2022-08-13 23:05 Harald Judt
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=83r11mnh7v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).