From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 42605@debbugs.gnu.org
Subject: bug#42605: 28.0.50; File lines in find-dired buffers not updated
Date: Thu, 30 Jul 2020 00:42:35 +0200 [thread overview]
Message-ID: <87365a6izo.fsf@web.de> (raw)
In-Reply-To: <7e79b76f-fe7f-498e-8373-8eba0c25579d@default> (Drew Adams's message of "Wed, 29 Jul 2020 14:53:36 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> > OTOH, when I delete a file in a buffer, dired could be smart enough to
> > guess that the current buffer does include the file.
>
> FWIW, I don't understand the last paragraph. What do
> you mean by "delete a file in a buffer"? Do you mean
> somehow delete a file (from disk) from a buffer that
> is visiting it? Or delete it from a Dired buffer?
> I'm guessing it's the latter, but in that case Dired
> does do that, doesn't it?
I hit D in the find-dired result buffer. Dired deletes the file but
it's not removed from the buffer.
> `find-dired' gives you a snapshot of what's on disk
> at a given time. Dired does that too, but for Dired
> there's an optional behavior of having its display
> auto-revert, to pick up any disk changes when you
> revisit the Dired buffer.
>
> Is that what you're requesting for `find-dired' too?
> If so, should it be turned on by the same option,
> `dired-auto-revert-buffer'? I can think that someone
> might well want a different option for it.
No, that's not what I want. That might be very slow, so it's no general
solution. And also not necessary I think.
Michael.
next prev parent reply other threads:[~2020-07-29 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:28 bug#42605: 28.0.50; File lines in find-dired buffers not updated Michael Heerdegen
2020-07-29 21:53 ` Drew Adams
2020-07-29 22:42 ` Michael Heerdegen [this message]
2020-07-29 23:16 ` Drew Adams
2020-08-25 18:15 ` Matt Huszagh
2020-08-25 18:34 ` Stefan Kangas
2020-07-29 22:52 ` 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=87365a6izo.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=42605@debbugs.gnu.org \
--cc=drew.adams@oracle.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.