unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: dired-jump keybinding and autoload
Date: Mon, 24 May 2010 19:00:35 +0300	[thread overview]
Message-ID: <87vdadl26v.fsf@mail.jurta.org> (raw)
In-Reply-To: <xbaiy6fao8oq.fsf@cam.ac.uk> (Leo's message of "Sun, 23 May 2010 17:59:49 +0100")

> If you choose other key, people who have been using dired-x will have
> difficult time and dired-x is shipped with emacs for a while now.

We could keep `C-x C-j' in dired-x, or after moving dired-jump out of
dired-x, change the default value of dired-bind-jump to nil.  I.e.
not to make it a global keybinding by default, so to not change the
current status quo.

Finding a better non-conflicting key is another question.  For instance,
there are many free keys on the M-g ("goto") prefix.  I remember some
suggestions were `M-g j', `M-g d', or `M-g f'.

Since `C-x C-j' is almost a duplicate of `C-x d' (they both
switch to the Dired buffer), maybe a better key for dired-jump
would be `C-x C-d'.

Does anyone use `list-directory' currently bound to `C-x C-d'?

> I think dired-jump should be moved out of dired-x. Those redefined
> functions should be properly merged too. Redefining functions are
> dependent on the order the library is loaded and causes confusion from
> time to time.

dired-jump uses another feature of dired-x - it toggles omitting with
dired-omit-mode.  So at the first step dired-omit-mode should be moved
out of dired-x before dired-jump.

-- 
Juri Linkov
http://www.jurta.org/emacs/



  reply	other threads:[~2010-05-24 16:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 12:59 dired-jump keybinding and autoload Stephen Berman
2008-05-08 14:12 ` Stefan Monnier
2008-05-08 14:36   ` David Kastrup
2008-05-08 16:08     ` Stephen Berman
2008-05-09 23:52       ` Juri Linkov
2010-05-18 22:59         ` Juri Linkov
2010-05-23 15:48           ` Wojciech Meyer
2010-05-23 16:04             ` Juri Linkov
2010-05-23 16:45               ` Drew Adams
2010-05-23 16:50                 ` Lennart Borgman
2010-05-23 17:11                   ` Drew Adams
2010-05-23 17:24                     ` Lennart Borgman
2010-05-23 18:14                       ` Drew Adams
2010-05-23 18:47                         ` Lennart Borgman
2010-05-23 20:56                           ` Drew Adams
2010-05-23 21:08                             ` Lennart Borgman
2010-05-24  1:01                   ` Stephen J. Turnbull
2010-05-24  1:30                     ` Lennart Borgman
2010-05-24  5:03                       ` Stephen J. Turnbull
2010-05-23 16:59               ` Leo
2010-05-24 16:00                 ` Juri Linkov [this message]
2010-05-24 16:17                   ` Lennart Borgman
2010-05-24 16:46                     ` Drew Adams
2010-05-24 16:53                       ` Lennart Borgman
2010-05-24 16:35                   ` Drew Adams
2010-05-24  5:05             ` Miles Bader
2010-05-24  7:19               ` Wojciech Meyer
2010-05-24 17:39                 ` Lennart Borgman
2010-05-25  6:35                 ` Miles Bader

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=87vdadl26v.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.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).