From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23171@debbugs.gnu.org
Subject: bug#23171: 25.0.92; Key binding conventions for all modifiers
Date: Thu, 31 Mar 2016 19:32:21 +0000 [thread overview]
Message-ID: <CAArVCkSi1xXuXCfrQUO1UHoQiE2zjA9hTEQ9VfN6kss+OYv2sw@mail.gmail.com> (raw)
In-Reply-To: <831t6qv492.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Do., 31. März 2016 um 21:26 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Thu, 31 Mar 2016 19:40:25 +0200
> >
> > The manual entry "Key binding conventions" talks only about a small
> > subset of possible key bindings, such as the C-c prefix and the function
> > keys. Keys with Meta, Super, Hyper, and Alt are not documented. The
> > manual should contain conventions/rules for all possible keys.
>
> I'm not sure I understand the essence of the report. There's a whole
> section (named, unsurprisingly, "Key Bindings") dedicated to key
> bindings, and a subsection there named "Modifier Keys" covers all the
> modifiers, AFAICT.
>
What I mean is a specification which combinations are reserved for the
user, minor modes, and major modes. Context is
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22604, where such an addition
was requested for C-c combinations. Here I request one for all keys.
[-- Attachment #2: Type: text/html, Size: 1452 bytes --]
next prev parent reply other threads:[~2016-03-31 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 17:40 bug#23171: 25.0.92; Key binding conventions for all modifiers Philipp Stephani
2016-03-31 19:25 ` Eli Zaretskii
2016-03-31 19:32 ` Philipp Stephani [this message]
2019-11-08 4:51 ` Stefan Kangas
2019-11-08 13:05 ` Eli Zaretskii
2020-01-15 5:55 ` Stefan Kangas
2020-01-26 14:36 ` Philipp Stephani
2020-01-26 16:07 ` Eli Zaretskii
2020-01-26 14:38 ` Philipp Stephani
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=CAArVCkSi1xXuXCfrQUO1UHoQiE2zjA9hTEQ9VfN6kss+OYv2sw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=23171@debbugs.gnu.org \
--cc=eliz@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).