From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: emacs-devel@gnu.org, ppaatt@aol.com
Subject: Re: bindings reserved for users
Date: Mon, 22 Apr 2002 13:29:01 +0200 [thread overview]
Message-ID: <vafit6kc6pu.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <200204201728.g3KHS3n01492@aztec.santafe.edu> (Richard Stallman's message of "Sat, 20 Apr 2002 11:28:03 -0600 (MDT)")
Richard Stallman <rms@gnu.org> writes:
> What about non-ascii characters? The characters themselves? C-c
> followed by such a character? C-c followed by C-X where X is such a
> character? M-X where X is such a character?
>
> Since such characters are not available on all terminals, the question
> is not very important. People won't want to use these keys in major
> modes or minor modes meant for general use. I don't think we need to
> settle it now.
I see you explained things in the lispref. I propose the following
patch to the Emacs manual: (What is the correct way to typeset
"i.e." in Texinfo source code?)
--- custom.texi.~1.47.~ Mon Apr 1 17:08:42 2002
+++ custom.texi Mon Apr 22 13:24:29 2002
@@ -1349,7 +1349,8 @@
key sequences are inconvenient to use.
As a user, you can redefine any key; but it is usually best to stick
-to key sequences that consist of @kbd{C-c} followed by a letter.
+to key sequences that consist of @kbd{C-c} followed by a (lowercase or
+uppercase) letter, i.e. a through z and A through Z.
These keys are ``reserved for users,'' so they won't conflict with any
properly designed Emacs extension. The function keys @key{F5} through
@key{F9} are also reserved for users. If you redefine some other key,
As a separate issue, I think if X is a nonascii character, one could
reserve C-c X for users and C-c C-X for modes. What do you think,
Richard?
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-04-22 11:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:14 bindings reserved for users Kai Großjohann
2002-04-18 18:44 ` Richard Stallman
2002-04-18 19:37 ` Kai Großjohann
2002-04-20 17:28 ` Richard Stallman
2002-04-22 11:29 ` Kai Großjohann [this message]
2002-04-22 18:34 ` Eli Zaretskii
2002-04-22 20:10 ` Simon Josefsson
2002-04-23 6:49 ` Eli Zaretskii
2002-04-23 19:29 ` Richard Stallman
2002-04-25 6:05 ` Richard Stallman
2002-04-25 11:13 ` Eli Zaretskii
2002-04-26 8:52 ` Florian Weimer
2002-04-23 10:48 ` Kai Großjohann
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 20:47 PPAATT
2002-04-20 12:13 PPAATT
2002-04-21 13:49 PPAATT
2002-04-22 7:47 ` Richard Stallman
2002-04-22 9:32 ` Stefan Monnier
2002-04-23 13:47 PPAATT
2002-04-24 12:45 PPAATT
2002-04-26 15:30 PPAATT
2002-04-26 15:45 ` 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
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=vafit6kc6pu.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=emacs-devel@gnu.org \
--cc=ppaatt@aol.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).