unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Hudson <phil.hudson@iname.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55301@debbugs.gnu.org
Subject: bug#55301: 27.2; RFE: Auto-create defcustom for declared minor mode keymap
Date: Sun, 8 May 2022 14:47:57 +0100	[thread overview]
Message-ID: <CAJ1MqVGNXQ154Gu36_cPjSWFownmurESQ4bDHHhEchENXYCg2A@mail.gmail.com> (raw)
In-Reply-To: <87pmkojlg7.fsf@gnus.org>

Not a built-in one, no, but it is not difficult to construct a composite
defcustom.  There are plenty of sequence types and a keybinding type to compose
with.

Perhaps Emacs *should* have a standard built-in keymap defcustom type, but that
would be the subject for a separate RFE.

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.

On Sun, 8 May 2022 at 12:46, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Phil Hudson <phil.hudson@iname.com> writes:
>
> > If nobody sees any benefit from the idea, I imagine the best thing is
> > to just close this.
>
> I just don't understand the request -- we don't have a Customize
> interface for altering keymaps anyway.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-08 13:47 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 [this message]
2022-05-09  9:34         ` Lars Ingebrigtsen
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=CAJ1MqVGNXQ154Gu36_cPjSWFownmurESQ4bDHHhEchENXYCg2A@mail.gmail.com \
    --to=phil.hudson@iname.com \
    --cc=55301@debbugs.gnu.org \
    --cc=larsi@gnus.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).