From: henning <henning.red@googlemail.com>
Subject: Re: dired in one buffer
Date: Fri, 18 Aug 2006 01:37:56 -0700 (PDT) [thread overview]
Message-ID: <5863516.post@talk.nabble.com> (raw)
In-Reply-To: <u64gtez8o.fsf@shared-files.de>
This does exactly what I wanted. Although I from other posts now realise how
easy it is to live without this extension by just redefining "^"
many thanks!
Torsten Mueller-3 wrote:
>
> henning <henning.red@googlemail.com> schrieb:
>
>> I would like dired to stay in the same buffer, e.g. when I go up one
>> directory I would like the present buffer to just clear and be
>> replaced by the content in the parent folder instead of opening a
>> new buffer. If find it quite annoying to have a stack of dired
>> buffers open after looking around in the directory tree... Does
>> anyone know how to implement that? Or am I missing something?
>
> You could use dired-single
>
> http://www.northbound-train.com/emacs.html#MyPackages
>
> T.M.
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>
>
--
View this message in context: http://www.nabble.com/dired-in-one-buffer-tf2114297.html#a5863516
Sent from the Emacs - Help forum at Nabble.com.
next prev parent reply other threads:[~2006-08-18 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5219.1155721985.9609.help-gnu-emacs@gnu.org>
2006-08-16 10:09 ` dired in one buffer Johan Bockgård
2006-08-16 10:44 ` Torsten Mueller
2006-08-18 8:37 ` henning [this message]
[not found] ` <mailman.5319.1155906765.9609.help-gnu-emacs@gnu.org>
2006-08-18 13:32 ` Torsten Mueller
2006-08-16 11:57 ` robert.thorpe
2006-08-16 16:19 Jay Bingham
2006-08-18 23:18 ` Drew Adams
2006-08-20 8:24 ` Dieter Wilhelm
2006-08-20 19:26 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 11:06 Bourgneuf Francois
2006-08-16 9:53 henning
2006-08-16 10:41 ` Peter Dyballa
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=5863516.post@talk.nabble.com \
--to=henning.red@googlemail.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).