From: Kaustuv <kaustuv@stanford.edu>
Subject: Re: Buffers in Dired
Date: 31 May 2003 10:46:03 -0700 [thread overview]
Message-ID: <m3r86fqaas.fsf_-_@crayt3e.stanford.edu> (raw)
Hi all,
I am using dired to navigate through the files of my home. But the
problem is the moment i move to a subdirectory dired creates a new
buffer for it. So ultimetly it turns out i have just too many buffers
open if i am locating a file buried deep my home directory sturcture.
Is there some configuration variable which shall tell it not to create
all these buffers but to work only from one buffer. In short all i want
is JUST ONE buffer for all my navigation.
Regards,
K.
next reply other threads:[~2003-05-31 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 17:46 Kaustuv [this message]
2003-05-31 19:48 ` Buffers in Dired Kai Großjohann
2003-05-31 20:33 ` Johan Bockgård
2003-05-31 21:43 ` Ed Cavazos
2003-06-01 3:36 ` Galen Boyer
2003-06-01 7:19 ` Peter Lee
2003-06-01 16:19 ` Buffers in Dired (Thanks) Kaustuv
2003-06-01 17:53 ` Buffers in Dired Galen Boyer
2003-06-01 18:05 ` Matthias Meulien
2003-06-02 5:28 ` Friedrich Dominicus
2003-06-02 6:00 ` David Masterson
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=m3r86fqaas.fsf_-_@crayt3e.stanford.edu \
--to=kaustuv@stanford.edu \
/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).