unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Jay Bingham" <b.jc-emacs@netzero.com>
Subject: RE: dired in one buffer
Date: Wed, 16 Aug 2006 16:19:50 GMT	[thread overview]
Message-ID: <20060816.092016.26494.579978@webmail51.nyc.untd.com> (raw)

On Wednesday, August 16, 2006 4:53 AM henning wrote:

> 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?

Missing something. :-)

The functionality is mostly already present in emacs.  The function 
dired-find-alternate-file (normally assigned to the 'a' key in dired-
mode) replaces the current buffer (the dired buffer) with the 
file/directory that the cursor is on.  When the function exits the 
dired buffer containing the original directory has been killed and 
the active buffer contains the file/directory that was opened.  

Going down in the directory tree is intuitive.  Going up the 
directory tree requires that the cursor be on the '..' entry in the 
dired buffer.

If you are used to using the '^' to navigate up the directory tree 
then you will either need to retrain yourself or will need to do some 
elisp programing to attach the functionality to the '^' key.  I 
looked at the function dired-up-directory (in dired.el) which is 
associated with the '^' key, it does not look like it would be too 
difficult to create your own function based on it and assign it to 
the '^' key in dired mode.

Good luck,
__
J_)
C_)ingham 


_____________________________________________________________________
PrivatePhone - FREE telephone number & voicemail.
A number so private, you can make it public.
http://www.privatephone.com

             reply	other threads:[~2006-08-16 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 16:19 Jay Bingham [this message]
2006-08-18 23:18 ` dired in one buffer Drew Adams
2006-08-20  8:24   ` Dieter Wilhelm
2006-08-20 19:26     ` Drew Adams
     [not found] <mailman.5219.1155721985.9609.help-gnu-emacs@gnu.org>
2006-08-16 10:09 ` Johan Bockgård
2006-08-16 10:44 ` Torsten Mueller
2006-08-18  8:37   ` henning
     [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
  -- 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=20060816.092016.26494.579978@webmail51.nyc.untd.com \
    --to=b.jc-emacs@netzero.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).