From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, rms@gnu.org,
emacs-devel@gnu.org, Kai.Grossjohann@CS.Uni-Dortmund.DE,
eliz@is.elta.co.il
Subject: Re: bindings reserved for users
Date: Fri, 26 Apr 2002 11:45:52 -0400 [thread overview]
Message-ID: <200204261545.g3QFjrk29922@rum.cs.yale.edu> (raw)
In-Reply-To: 8f.1b0ba8cd.29facc94@aol.com
> > > C-h i m emacs RET m keymaps RET
> ...
> > The experience until now is that
> > non-ASCII letters are never used
> > by major modes or minor modes,
> > so we [haven't needed] to decide
> > whether they should be reserved for the user or not.
>
> Curious. I can make sense of the RMS English this way,
> thank you ... except I see you didn't write exactly this.
> Where I write [] brackets, you actually wrote "we don't
> need" to decide?
I don't care about the distinction. I think my point
was clear enough.
> What first drew my attention here was me failing to find
> any commonly available shifted key left reserved
> for the user by GNU Emacs.
That's because you misunderstood the doc.
`E' is a letter so C-c E is reserved for the user.
Or I misunderstand what you mean by "available shifted key".
> I think [ C-h i m emacs RET m keymaps RET ] tells me
> Emacs reserves for my use only the single keys
> F5 thru F9: no single key that I can hit without looking.
Indeed.
> If M-n M-o M-p are not candidates to be reserved for the
> user, how about the other single keys not bound by
> Emacs 20.7.1 by default i.e.
> C-` C-= C-; C-' C-, C-.
Feel free to use them (note that they most likely won't be available
(or only painfully which would defeat the purpose) in `emacs -nw').
But of course since they are not reserved for your use, you might
some day find that some mode uses them (for example X-Symbol uses C-=).
You can also use M-o which seems to be pretty much completely unused
(contrary to M-p and M-n which are very often used).
Many people use non-reserved key bindings all the time.
Stefan
next prev parent reply other threads:[~2002-04-26 15:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 15:30 bindings reserved for users PPAATT
2002-04-26 15:45 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-24 12:45 PPAATT
2002-04-23 13:47 PPAATT
2002-04-21 13:49 PPAATT
2002-04-22 7:47 ` Richard Stallman
2002-04-22 9:32 ` Stefan Monnier
2002-04-20 12:13 PPAATT
2002-04-18 20:47 PPAATT
2002-04-17 14:14 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
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
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=200204261545.g3QFjrk29922@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).