From: Harald Judt <h.judt@gmx.at>
To: help-gnu-emacs@gnu.org
Subject: Re: dired cons bug?
Date: Thu, 11 Aug 2022 11:23:52 +0200 [thread overview]
Message-ID: <35b2cf5e-a1ef-109f-0eba-4f8e30655813@gmx.at> (raw)
In-Reply-To: <cebed6c6-16b9-0ec6-a05d-a03337ee1c9e@gmx.at>
[-- Attachment #1.1: Type: text/plain, Size: 1852 bytes --]
Am 10.08.22 um 13:26 schrieb Harald Judt:
> Hi,
>
> I have a question regarding using dired programmatically in Emacs 28.1. Say I
> do the following call to open a dired buffer and insert the files:
>
> (dired (cons "/home/user" '("/home/user/tmp/test/a/a"
> "/home/user/tmp/test/b/b" "/home/user/tmp/test/c/c")))
>
> It works fine, I get a nice listing and can move around like expected, mark
> files and try to delete them. Now it gets interesting: Usually after hitting
> "x" to execute, then confirming the deletion, the buffer will refresh. But not
> in this case, not when I open dired using the cons above. I can revert the
> buffer using "g".
>
> Note that when I simply do (dired "/home/user/tmp/test"), then insert the
> subdir to show the files and delete them, this is not reproducible. The buffer
> will be refreshed immediately after the delete operation completes.
>
> Why? Am I missing something? Is this a (known) bug or expected behaviour? I've
> tried with emacs -Q, so it seems to be no configuration problem.
>
> Regards,
> Harald
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?
Harald
--
`Experience is the best teacher.'
PGP Key ID: 4FFFAB21B8580ABD
Fingerprint: E073 6DD8 FF40 9CF2 0665 11D4 4FFF AB21 B858 0ABD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-11 9:23 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 [this message]
2022-08-12 5:50 ` Eli Zaretskii
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=35b2cf5e-a1ef-109f-0eba-4f8e30655813@gmx.at \
--to=h.judt@gmx.at \
--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).