From: robert.thorpe@antenova.com (Rob Thorpe)
Subject: Re: Keep dired from creating new buffers.
Date: 15 Dec 2003 10:15:44 -0800 [thread overview]
Message-ID: <1a61f7e5.0312151015.6961b90c@posting.google.com> (raw)
In-Reply-To: brcpjk$hcr$1@fred.mathworks.com
"Bora" <nobody@nospam.none> wrote in message news:<brcpjk$hcr$1@fred.mathworks.com>...
> Whenever I navigate through (sub)directories in "dired", I get a new buffer
> for each directory. This quickly creates a large number of buffers in
> emacs. Is there a way to keep dired from doing this, and instead use only
> one buffer and update its content if I move through directories.
>
> Thanks
> Bora
The most satisfactory method I've found is to use dired like this:
Normally press 'a' on a subdir which replaces the current dired buffer
with the buffer of that subdir.
Use 'enter' when you actually want a new dired buffer, sometimes it's
useful
Use 'i' which inserts the subdir into the current buffer when you know
the directory listing will be fairly short. To remove these when
you've finished use C-u k next to them.
prev parent reply other threads:[~2003-12-15 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 16:15 Keep dired from creating new buffers Bora
2003-12-12 19:44 ` Yoni Rabkin
2003-12-15 9:50 ` Sébastien Kirche
2003-12-12 19:55 ` Ekkehard Görlach
2003-12-12 19:59 ` Henrik Enberg
2003-12-15 18:15 ` Rob Thorpe [this message]
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=1a61f7e5.0312151015.6961b90c@posting.google.com \
--to=robert.thorpe@antenova.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.
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).