From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20992@debbugs.gnu.org
Subject: bug#20992: 25.0.50; `virtual-dired': (1) doc typo, (2) unclear
Date: Thu, 02 Dec 2021 17:25:52 +0100 [thread overview]
Message-ID: <871r2vrn1r.fsf@web.de> (raw)
In-Reply-To: <87r1av10am.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 02 Dec 2021 16:41:53 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It wasn't obvious to me, so please do go ahead and add that to the doc
> string. 😄
I...[loses courage] ok, but note this is not something I know, it is
something I did (and it seemed to work). Are we sure that it doesn't
only work by accident most of the time? For me this is just the, more
or less, only use case for virtual dired buffers: I can remember marks
by just saving a dired buffer and reopen it later with virtual-dired to
continue working with the files in it.
AFAIR this didn't ever work so super sexy - Emacs didn't recognize the
contents as (virtual) dired, I have to M-x virtual-dired explicitly, and
this command modifies the buffer (though it didn't touch the text), so I
have to save it again... I guess there is at least room for improvement
before we advertise this method in the docstring.
Michael.
next prev parent reply other threads:[~2021-12-02 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:20 bug#20992: 25.0.50; `virtual-dired': (1) doc typo, (2) unclear Drew Adams
2015-07-06 17:49 ` Drew Adams
2020-03-31 0:30 ` Michael Heerdegen
2020-03-31 1:23 ` Drew Adams
2020-03-31 2:53 ` Michael Heerdegen
2021-12-02 9:48 ` Lars Ingebrigtsen
2021-12-02 14:59 ` Michael Heerdegen
2021-12-02 15:41 ` Lars Ingebrigtsen
2021-12-02 16:25 ` Michael Heerdegen [this message]
2021-12-02 16:45 ` Lars Ingebrigtsen
2019-09-29 22:44 ` Stefan Kangas
2021-12-02 23:14 ` Phil Sainty
2021-12-02 23:47 ` Michael Heerdegen
2021-12-02 23:50 ` Phil Sainty
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=871r2vrn1r.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=20992@debbugs.gnu.org \
--cc=larsi@gnus.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.