From: Paul Smith <psmith@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Reserved keymap not reserved anymore?
Date: Sun, 17 Nov 2013 18:18:30 -0500 [thread overview]
Message-ID: <1384730310.2758.338.camel@homebase> (raw)
In-Reply-To: <874n7a6424.fsf@web.de>
On Sun, 2013-11-17 at 23:45 +0100, Michael Heerdegen wrote:
> Drew, don't you think it belongs in the user manual? This is not a
> programmer's issue - a user should know which keys he can use for his
> bindings, and which are reserved. Do I miss something?
I think it belongs in both. In the Emacs manual, as you say, so users
know about it. And in the Elisp manual so people writing new modes,
etc. know about the reservation and don't use it.
My $0.02.
next prev parent reply other threads:[~2013-11-17 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 20:57 Reserved keymap not reserved anymore? Paul Smith
2013-11-17 21:14 ` Drew Adams
2013-11-17 21:32 ` Paul Smith
2013-11-17 22:45 ` Michael Heerdegen
2013-11-17 23:18 ` Paul Smith [this message]
2013-11-18 0:58 ` Drew Adams
2013-11-18 1:02 ` Drew Adams
2013-11-18 3:40 ` Michael Heerdegen
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=1384730310.2758.338.camel@homebase \
--to=psmith@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).