From: Lennart Borgman <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Juri Linkov <juri@jurta.org>,
Wojciech Meyer <wojciech.meyer@googlemail.com>,
emacs-devel@gnu.org
Subject: Re: dired-jump keybinding and autoload
Date: Sun, 23 May 2010 19:24:40 +0200 [thread overview]
Message-ID: <AANLkTimBOFlSzLuKUvKiAWz_QL9cPgjTfhKklb61GXn3@mail.gmail.com> (raw)
In-Reply-To: <D30334D6F5E246919C9EE7B448F6DC0E@us.oracle.com>
On Sun, May 23, 2010 at 7:11 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> More important: C-x C-j is reserved for Emacs internal use if I
>> understand it correctly.
>
> No, I don't see that anywhere. Why would that be the case?
>
>> See (info "(elisp) Key Binding Conventions"). I might be wrong since
>> that page does not mention C-x, but I think it should.
>
> You ask us to visit that node, but there is nothing there supporting your claim
> - which you subsequently admit. Just what would you like us to look for in that
> node?
Please do not exaggerate. I want you to look at the keys reserved for
major modes!
>> That C-x today happens to be a bad choice (because of CUA) is another
>> thing.
>
> Sure is. Unrelated, irrelevant, unimportant.
Why? This just looks like a rant.
> C-x today, yesterday, and tomorrow is an _excellent_ choice as an Emacs key
> prefix. It is easy-to-hand. And it has been conventional in Emacs (and even
> beyond) for over 30 years.
We have different opinions. Saying that it is an excellent choice is
an exaggeration. It is not an excellent choice in my opinion.
> Saying that C-x is a bad choice because of CUA is like saying that driving on
> the right side of the road is a bad choice because of Britain (or Japan or
> India... - no flames please) - http://www.brianlucas.ca/roadside/. When in
> CUA-land, follow the rules of the CUA road, but don't expect folks across the
> border to do the same.
That would be nice, but would not that mean that all key bindings
should be changed when cua-mode is on? Or do you think CUA land is
outside of Emacs?
> There is absolutely nothing wrong with users or 3rd-party code using the C-x
> prefix. Or else there is a new restriction/convention that I am not aware of.
>
> The conventions stated in `(elisp) Key Binding Conventions' are long-standing
> and pretty carefully thought out. There are enough such restrictions, IMO. I
> do not support adding C-x to any list of bindings "reserved for Emacs internal
> use".
All C-x bindings are absent from that page. I guess you do not mean
that a major mode could use any key bindings starting with C-x?
I have assumed that C-x is not mentioned because it is reserved for
Emacs. If not, then it should be mentioned on that info page to
clarify things.
But my opinion is very clear: Recommend that 3rd party libraries
should not use C-x as a prefix key.
next prev parent reply other threads:[~2010-05-23 17:24 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimBOFlSzLuKUvKiAWz_QL9cPgjTfhKklb61GXn3@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=wojciech.meyer@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.