From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Noah Lavine <noah549@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Key Mapping Proposal
Date: Sun, 17 Jan 2010 14:49:19 +0900 [thread overview]
Message-ID: <87aawdth5s.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <16d22e431001161041v2adb2ec9odd6ee6f5b528d78c@mail.gmail.com>
Noah Lavine writes:
> However, it seems like my question and Teemu Likonen's reply show that
> the functionality isn't well enough documented yet.
It is well documented I think, but in the Emacs-Lisp manual.
It's a matter of judgment (and mine doesn't really matter much on this
list :-), but IMHO it doesn't belong in the Emacs User manual. Again
I commend to you the study of CUA mode, which has been endlessly
controversial (partly for reasons of free software advocacy, of
course, but also for technical reasons) exactly because trying to move
as few as four bindings forces changes throughout the keymap, and then
of course it encourages requests for more CUA compatibility, in mouse
gestures as well, etc. IOW, any such change is equivalent in
difficulty to writing a simple major mode (and can be substantially
more difficult if you want to contribute it to the community, because
to get much uptake you need to compromise with others' "essential"
keybindings.
YMMV; I offer my opinion to give you an idea of what kind of contrary
opinion may be out there so you can deal with it in advance, not to
discourage you from trying.
> I think a good solution would be an info node that explains this
> mechanism which would be linked from the Customization->Key Bindings
> node, with a list of the generic functions that are commonly the
> target of keybindings,
Doing C-h b in *scratch* gives a pretty close approximation IMO. Try
it and let us know. Note that although the default global keymap is
one of the most stable features of the Emacs UI, it does change
occasionally. Since Emacs is capable of generating it on the fly, I
think it's best to point to the functionality of C-h b rather than put
a table in the manual.
In addition, I would suggest a link to the node on keymaps in the
Emacs Lisp manual (which Emacs doesn't install by default, or maybe
that's just MacPorts, grr).
I think that what you'll find if you browse the help for help is that
most of the information you've mentioned is oly a few keystrokes away.
It would be useful to provide a summary of how to get the information
that you think is useful in the node in the Emacs User guide (although
I still think that the detailed information belongs in the Lisp
Reference).
next prev parent reply other threads:[~2010-01-17 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 0:03 Key Mapping Proposal Noah Lavine
2010-01-16 7:57 ` Fabian Ezequiel Gallina
2010-01-16 8:17 ` Stephen J. Turnbull
2010-01-16 18:41 ` Noah Lavine
2010-01-17 5:49 ` Stephen J. Turnbull [this message]
2010-01-16 8:25 ` Teemu Likonen
2010-01-16 14:22 ` Eric M. Ludlam
2010-01-16 19:28 ` Stefan Monnier
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=87aawdth5s.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=noah549@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 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.