From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Hudson <phil.hudson@iname.com>
Cc: 55301@debbugs.gnu.org
Subject: bug#55301: 27.2; RFE: Auto-create defcustom for declared minor mode keymap
Date: Mon, 09 May 2022 11:34:07 +0200 [thread overview]
Message-ID: <87pmkncank.fsf@gnus.org> (raw)
In-Reply-To: <CAJ1MqVGNXQ154Gu36_cPjSWFownmurESQ4bDHHhEchENXYCg2A@mail.gmail.com> (Phil Hudson's message of "Sun, 8 May 2022 14:47:57 +0100")
Phil Hudson <phil.hudson@iname.com> writes:
> What I am proposing is something along the lines of this: when a mode
> (major or minor, it's strictly irrelevant) declares a keymap, part of
> the processing of the expansion of the mode definition should include
> a defcustom enabling the user to customize that keymap using the
> Customize UI, rather than (only) by writing elisp code. In other
> words, where foo-mode-map is currently implemented (I assume) using a
> defvar, that should change to a defcustom. That's really all I'm
> suggesting: change the defvar (or whatever) to a defcustom.
Emacs doesn't have a Customize UI to alter keymaps, so changing defvars
to defcustom isn't currently useful (because there's no :type that
could be used other than `sexp').
It would be possible to create such an UI, of course, but it would work
quite differently than all other Customize widgets. I don't think
anybody wants to have the entire definitions of keymaps in their .emacs
files -- they want to add a keystroke or remove a keystroke or two, and
that's it. (And, besides, they want to get new keystrokes that are
added to the maps.)
But it'd be nice to have; sure.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-09 9:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 14:07 bug#55301: 27.2; RFE: Auto-create defcustom for declared minor mode keymap Phil Hudson
2022-05-07 15:34 ` Lars Ingebrigtsen
2022-05-07 16:49 ` Phil Hudson
2022-05-08 11:46 ` Lars Ingebrigtsen
2022-05-08 13:47 ` Phil Hudson
2022-05-09 9:34 ` Lars Ingebrigtsen [this message]
2022-05-09 9:52 ` Phil Hudson
2022-05-09 9:54 ` Lars Ingebrigtsen
2022-05-09 10:02 ` Phil Hudson
2022-05-09 13:39 ` Robert Pluim
2022-05-09 15:04 ` Phil Hudson
2022-05-17 16:03 ` Phil Hudson
2022-05-17 16:13 ` Robert Pluim
2022-05-17 17:27 ` Lars Ingebrigtsen
2022-05-18 7:13 ` Robert Pluim
2022-05-18 10:59 ` Phil Hudson
2022-05-18 11:29 ` Lars Ingebrigtsen
2022-05-18 13:39 ` Phil Hudson
2022-05-20 22:32 ` Richard Stallman
2022-05-09 9:55 ` Phil Hudson
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=87pmkncank.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55301@debbugs.gnu.org \
--cc=phil.hudson@iname.com \
/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).