unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20992@debbugs.gnu.org
Subject: bug#20992: 25.0.50; `virtual-dired': (1) doc typo, (2) unclear
Date: Tue, 31 Mar 2020 02:30:52 +0200	[thread overview]
Message-ID: <87sghpxt4z.fsf@web.de> (raw)
In-Reply-To: <3d083fa4-c6fb-4890-944f-19a206b4c035@default> (Drew Adams's message of "Mon, 6 Jul 2015 10:49:38 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> 4. It's not clear from the doc just how `virtual-dired' changes
> Dired mode.  It doesn't seem particularly "virtual", but it's not
> clear what is meant by that word here.
>
> Seems that this is in fact just Dired mode, and that it is the
> opposite of a virtual Dired mode: it puts an ordinary `ls'
> listing into Dired mode, no?

More or less yes, I guess.  My impression after reading the available
docs, and when trying to use it, is that the purpose is to get a dired
like listing from somewhere else, e.g. an external source, or from a
saved file (e.g. a dired buffer from a later Emacs session saved to a
file) into a dired-like mode to have access to some of its commands.  It
is virtual in the sense that the contents do not necessarily need to
reflect the contents of an existing directory.  This is only checked if
you switch to the real dired mode.  A better wording might have been
"offline" dired mode or so.

If saving dired buffers is indeed one of the purposes, this case would
also need some fine tuning: when opening the saved file, it is currently
just in fundamental-mode.  And after switching to virtual-dired the
buffer is immediately marked as modified and you need to save or discard
changes when you want to kill the buffer although you didn't change
anything at all.

Michael.





  reply	other threads:[~2020-03-31  0:30 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 [this message]
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
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

  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=87sghpxt4z.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=20992@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).