From: Philip Kaludercic <philipk@posteo.net>
To: Gregory Heytings <gregory@heytings.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: PROPOSAL: Repurpose one key and reserve it for third-party packages
Date: Fri, 12 Feb 2021 19:16:50 +0100 [thread overview]
Message-ID: <877dndgnhp.fsf@posteo.net> (raw)
In-Reply-To: <329d68a5ed4f4c7e84fb@heytings.org> (Gregory Heytings's message of "Fri, 12 Feb 2021 17:54:52 +0000")
[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]
Gregory Heytings <gregory@heytings.org> writes:
>> My suggestion is based on the introduction of two variables: One for
>> packages to formally specify their suggestions for what keys to
>> bind, what hooks to modify, what options to set, etc. and one for
>> users to declare if they are interested or not.
>>
>> The patch I added to a message proposed that eg. Magit wouldn't
>> write something like
>>
>> ;;;###autoload
>> (global-set-key (kbd "C-x g") #'magit-status)
>>
>> (I'm oversimplifying, their code is more complex), but instead they
>> add a line like
>>
>> ;;;###autoload
>> (add-to-list 'pacakge-configuration-suggestions
>> '(magit ; package name
>> (key ; what type of suggestion
>> "C-x g" ; what key to bind the following to
>> magit-status ; what command to bind
>> )))
>>
>
> I'm fine with this in principle, but it doesn't answer the question.
> In the above example Magit would suggest "C-x g". It can do this
> because at the moment that key isn't used by Emacs. There is no
> guarantee that that key will not at some point be reclaimed by Emacs.
> It cannot suggest a "C-c LETTER" key, these are AFAIU strictly
> reserved for users in their configuration files, and there are not
> enough available keys there so this cannot be a long term solution
> anyway. So what keys can it suggest? This, and only this, is what the
> proposal is about.
My reading of the guideline on "C-c LETTER" is that a major/minor mode
shouldn't bind C-c LETTER to a command, so that it overshadows whatever
is bound globally to C-c LETTER. But a system like what I propose just
generates to configuration *for* the user, in a user file in which case
the guideline doesn't apply. That's what I mean by avoiding the need for
an extra key-space.
Of course, if some way could be found to reserve a prefix for
third-party packages, pacakge-configuration-suggestions could always
use this too -- my suggestion just anticipates that this will probably
not happen and tries to solve the problem in a different way.
--
Philip K.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2021-02-12 18:16 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` PROPOSAL: Repurpose one key and reserve it for third-party packages 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 [this message]
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 15:39 ` Nothing is the list - " Jean Louis
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 21:37 ` PROPOSAL: Repurpose one key (why only one?) " Jean Louis
2021-02-13 23:55 ` Philip Kaludercic
2021-02-14 6:19 ` Jean Louis
2021-02-14 6:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 8:06 ` Jean Louis
2021-02-14 18:30 ` [External] : " Drew Adams
2021-02-14 19:21 ` Jean Louis
2021-02-14 19:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 23:30 ` Drew Adams
2021-02-15 0:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-15 5:59 ` Jean Louis
2021-02-14 17:59 ` Gregory Heytings
2021-02-14 18:14 ` libraries (was: Re: PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages) Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 18:23 ` PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages Philip Kaludercic
2021-02-14 21:37 ` Gregory Heytings
2021-02-15 0:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-15 5:02 ` Robert Thorpe
2021-02-15 11:08 ` Gregory Heytings
2021-02-17 9:07 ` Robert Thorpe
2021-02-20 17:50 ` Gregory Heytings
2021-02-14 18:30 ` [External] : " Drew Adams
2021-02-14 18:50 ` Gregory Heytings
2021-02-14 19:24 ` Jean Louis
2021-02-14 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 23:30 ` [External] : " Drew Adams
2021-02-13 10:05 ` PROPOSAL: Repurpose one key " 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 ` [External] : " Drew Adams
2021-02-11 16:58 ` Drew Adams
2021-02-11 16:59 ` Leo Butler
2021-02-15 19:01 Gregory Heytings
2021-02-15 19:55 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2021-02-08 10:02 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-10 22:54 ` Francis Belliveau
2021-02-09 6:31 ` Jean Louis
2021-02-09 9:13 ` Gregory Heytings
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-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-09 8:13 ` Marcin Borkowski
2021-02-09 9:13 ` Gregory Heytings
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=877dndgnhp.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=gregory@heytings.org \
--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).