From: Gregory Heytings <gregory@heytings.org>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: PROPOSAL: Repurpose one key and reserve it for third-party packages
Date: Tue, 09 Feb 2021 09:13:08 +0000 [thread overview]
Message-ID: <8ed9b43502bad8cafcf1@heytings.org> (raw)
In-Reply-To: <YCIsQ0idChCjH8Ds@protected.rcdrun.com>
>> The current key binding conventions (see `(elisp) Key Binding
>> Conventions') reserve keys for users, for major modes and for minor
>> modes, but not for third-party packages [1].
>
> In my understanding those third party packages usually define major or
> minor modes so the reservation of keys for third party packages is thus
> already supported that way.
>
That's not correct, many packages (not all of them, but many) implement
commands that are intended to be globally bound. The "org-capture"
command is an example. A package implementing advance bookmark commands
is another one, a packages implementing a dictionary search command is yet
another one.
>
> There are more than one keys reserved already in the manner you
> described such as those reserved for users can be proposed and used by
> third party packages, including those for minor and major modes, they
> can be used by third party packages.
>
Third-party packages cannot do that, and they do not do that. A
third-party package cannot bind a key C-c LETTER key, it can at best
advise its users to do so. It's what Org-mode does.
>
> Maybe one could make a package that changes the prefix key or various
> packages or the package that could "see" which packages are used and
> which of them need positioning of their prefix keys. Then such package
> could ask user with proposal:
>
> - C-c bind prefix key for Org functions
>
> - C-, bind prefix for Magit functions
>
> Approve or change above y/n?
>
The first question is not an allowed one, C-c can only be used by users.
The second question is not a good one, C-, cannot be used in terminals.
next prev parent reply other threads:[~2021-02-09 9:13 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 10:02 PROPOSAL: Repurpose one key and reserve it for third-party packages Gregory Heytings
2021-02-08 16:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-08 22:01 ` Francis Belliveau
2021-02-09 0:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 8:36 ` "Windows" key [was: Repurpose one key and reserve it for third-party] packages tomas
2021-02-10 22:54 ` PROPOSAL: Repurpose one key and reserve it for third-party packages Francis Belliveau
2021-02-09 6:31 ` Jean Louis
2021-02-09 9:13 ` Gregory Heytings [this message]
2021-02-10 11:17 ` Jean Louis
2021-02-09 17:13 ` [External] : " Drew Adams
2021-02-09 17:49 ` Gregory Heytings
2021-02-09 18:12 ` Drew Adams
2021-02-09 19:23 ` Gregory Heytings
2021-02-09 20:52 ` [External] : " Drew Adams
2021-02-09 21:15 ` Gregory Heytings
2021-02-09 21:47 ` [External] : " Drew Adams
2021-02-09 22:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 22:58 ` Drew Adams
2021-02-09 23:23 ` Drew Adams
2021-02-09 23:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-10 11:07 ` Gregory Heytings
2021-02-10 9:05 ` Robert Thorpe
2021-02-10 14:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-10 14:59 ` Gregory Heytings
2021-02-10 11:33 ` [External] : " Jean Louis
2021-02-10 11:41 ` Thibaut Verron
2021-02-10 15:29 ` Eli Zaretskii
2021-02-10 11:30 ` Jean Louis
2021-02-09 8:13 ` Marcin Borkowski
2021-02-09 9:13 ` Gregory Heytings
[not found] <7ef75c33936136eb3a20@heytings.org>
[not found] ` <8735y56naf.fsf@posteo.net>
[not found] ` <8ed9b43502ae9a36b057@heytings.org>
[not found] ` <87tuqk6d9d.fsf@posteo.net>
[not found] ` <3966473cc1ab9f104724@heytings.org>
2021-02-10 23:35 ` Philip K.
2021-02-11 8:45 ` Gregory Heytings
2021-02-11 13:53 ` Philip K.
2021-02-11 15:47 ` Philip K.
2021-02-11 15:59 ` Gregory Heytings
2021-02-11 16:20 ` Philip K.
2021-02-11 17:48 ` Gregory Heytings
2021-02-11 18:34 ` Philip K.
2021-02-11 21:15 ` Gregory Heytings
2021-02-11 22:48 ` Philip K.
2021-02-12 0:01 ` Gregory Heytings
2021-02-12 10:27 ` Philip K.
2021-02-12 11:59 ` Gregory Heytings
2021-02-12 13:23 ` Philip K.
2021-02-12 13:54 ` Gregory Heytings
2021-02-12 14:09 ` Philip Kaludercic
2021-02-12 16:04 ` Gregory Heytings
2021-02-12 17:25 ` Philip Kaludercic
2021-02-12 17:54 ` Gregory Heytings
2021-02-12 18:16 ` Philip Kaludercic
2021-02-12 21:48 ` Gregory Heytings
2021-02-13 0:37 ` Philip Kaludercic
2021-02-13 8:33 ` Gregory Heytings
2021-02-13 9:09 ` Philip Kaludercic
2021-02-13 13:06 ` Gregory Heytings
2021-02-13 14:28 ` Philip Kaludercic
2021-02-13 15:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 16:08 ` Philip Kaludercic
2021-02-13 15:02 ` Gregory Heytings
2021-02-13 15:21 ` Jean Louis
2021-02-13 15:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 20:14 ` Philip Kaludercic
2021-02-13 20:58 ` Jean Louis
2021-02-13 21:18 ` Gregory Heytings
2021-02-13 21:32 ` Philip Kaludercic
2021-02-13 10:05 ` Jean Louis
2021-02-13 8:24 ` Jean Louis
2021-02-13 12:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 14:26 ` Jean Louis
2021-02-13 15:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:24 ` Jean Louis
2021-02-13 15:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:45 ` Jean Louis
2021-02-12 4:45 ` Robert Thorpe
2021-02-12 9:58 ` Philip K.
2021-02-11 16:59 ` Leo Butler
-- strict thread matches above, loose matches on Subject: below --
2021-02-15 19:01 Gregory Heytings
2021-02-15 19:55 ` Dmitry Gutov
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=8ed9b43502bad8cafcf1@heytings.org \
--to=gregory@heytings.org \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@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.
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).