From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Howard Melman <hmelman@gmail.com>, 30978@debbugs.gnu.org
Subject: bug#30978: 25.3; Suggestion: define-minor-mode should define mode-lighter variable
Date: Wed, 28 Jul 2021 22:00:49 +0200 [thread overview]
Message-ID: <87sfzyi4y6.fsf@gmail.com> (raw)
In-Reply-To: <87o8ambgkw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 28 Jul 2021 17:31:27 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It's already pretty easy to just alter the lighters -- just say:
>
> (setcar (cdr (assoc 'foo-mode minor-mode-alist)) "whatever")
Manipulating minor-mode-alist is not that hard indeed; there are some
sources of hassle though:
(1) figuring out the name of the mode variable (e.g. auto-fill-function,
defining-kbd-macro);
(2) some modes seem not to add their variables to minor-mode-alist for
some reason (e.g. caps-lock-mode on GNU ELPA), so this recipe does
not work (neither does delight); one needs to fallback to
add-to-list.
Nothing too herculean, but I'm sure some users would appreciate a
built-in function to figure out this stuff for them.
(And IIUC, solving this with a function, rather than automatically
creating variables for each minor mode, would address your concern about
bloat, since any added bloat would be opt-in)
prev parent reply other threads:[~2021-07-28 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 20:11 bug#30978: 25.3; Suggestion: define-minor-mode should define mode-lighter variable Howard Melman
2019-07-14 13:40 ` Lars Ingebrigtsen
[not found] ` <CADwFkmk-oFgHAwgcZ=-utkBU303x4vF9c9vkuUfpkPinL7Q0KQ@mail.gmail.com>
2020-08-23 12:22 ` Lars Ingebrigtsen
2021-06-25 14:27 ` Lars Ingebrigtsen
2021-06-25 22:57 ` Phil Sainty
2021-07-25 7:59 ` Lars Ingebrigtsen
2021-07-25 16:43 ` Howard Melman
2021-07-28 15:31 ` Lars Ingebrigtsen
2021-07-28 19:10 ` Howard Melman
2021-07-29 12:11 ` Lars Ingebrigtsen
2021-07-28 20:00 ` Kévin Le Gouguec [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfzyi4y6.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=30978@debbugs.gnu.org \
--cc=hmelman@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.