From: Phil Hudson <phil.hudson@iname.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 55301@debbugs.gnu.org
Subject: bug#55301: 27.2; RFE: Auto-create defcustom for declared minor mode keymap
Date: Mon, 9 May 2022 16:04:26 +0100 [thread overview]
Message-ID: <CAJ1MqVE9qU8wxDiNRPL6nYwR6F64kc8ceki-YRNX_OKBR6ENAw@mail.gmail.com> (raw)
In-Reply-To: <87ee123jwq.fsf@gmail.com>
On Mon, 9 May 2022 at 14:39, Robert Pluim <rpluim@gmail.com> wrote:
>
> >>>>> On Mon, 9 May 2022 11:02:20 +0100, Phil Hudson <phil.hudson@iname.com> said:
>
> Phil> Isn't that exactly the right place for declarative personal preferences?
>
> Yes, but if a keymap were a defcustom, then the whole keymap would be
> in your .emacs, and you would not receive any updates if the keymap
> definition changed, since that affects the *default* defcustom value.
True that, and I had not thought of it, but now that I have, I still
don't see it as necessarily confounding. Doesn't the same objection
(if it is one) apply to *every* defcustom? Is that not the risk that
the user takes when they change any custom option, and the risk that
every dev takes when they introduce a defcustom?
> Now if you wanted to define a defcustom type for changing bindings in an
> existing keymap, thatʼs a different proposition (and we already have
> define-key, so Iʼm not so sure of the utility).
That is exactly what I (think I) want. The utility is admittedly
marginal but perhaps not trivial. It's the difference between a
declarative approach, which I take to be intrinsically more accessible
and intuitive, especially to non-programmers, versus an imperative
one. It's essentially the case for custom options in general.
I suppose my maximalist claim would be that mode-defined keymaps are
self-evidently customize options that have somehow historically been
accidentally overlooked. I'm not entirely convinced myself, though.
Maybe we should just let it sit for a while. There's obviously
something about it that doesn't *feel* right to people with deeper
insight than I have.
next prev parent reply other threads:[~2022-05-09 15:04 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
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 [this message]
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=CAJ1MqVE9qU8wxDiNRPL6nYwR6F64kc8ceki-YRNX_OKBR6ENAw@mail.gmail.com \
--to=phil.hudson@iname.com \
--cc=55301@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.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).