From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 23171@debbugs.gnu.org, stefan@marxist.se
Subject: bug#23171: 25.0.92; Key binding conventions for all modifiers
Date: Sun, 26 Jan 2020 18:07:19 +0200 [thread overview]
Message-ID: <838slup5fs.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkSgTQB4rO-eDszqXMNVjuQnBfhtMPmAPDSXMuR62_ga2Q@mail.gmail.com> (message from Philipp Stephani on Sun, 26 Jan 2020 15:36:08 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 26 Jan 2020 15:36:08 +0100
> Cc: Stefan Kangas <stefan@marxist.se>, 23171@debbugs.gnu.org
>
> > FWIW, I don't see any need for any further specifications. The manual
> > says what keys to reserve; all those which aren't mentioned, including
> > with modifiers, aren't reserved.
>
> What does it mean for a key sequence to be unreserved? Anybody can use
> it for any purpose?
Yes, AFAIU.
> If so, how do we prevent clashes between these unreserved sequences?
We don't. It's up to the authors of the various packages to make
sure they don't step on keybindings of any other packages, except if
those other packages can never be used with this package. What else
can we do?
next prev parent reply other threads:[~2020-01-26 16:07 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838slup5fs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23171@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
--cc=stefan@marxist.se \
/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.