From: Lars Ingebrigtsen <larsi@gnus.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 30978@debbugs.gnu.org
Subject: bug#30978: 25.3; Suggestion: define-minor-mode should define mode-lighter variable
Date: Sun, 14 Jul 2019 15:40:36 +0200 [thread overview]
Message-ID: <874l3ou42z.fsf@mouse.gnus.org> (raw)
In-Reply-To: <C0EA6366-1848-4EF9-A963-9197E672B4E6@gmail.com> (Howard Melman's message of "Wed, 28 Mar 2018 16:11:52 -0400")
Howard Melman <hmelman@gmail.com> writes:
> Some packages define a user option to let users configure
> the lighter string used in the mode-line, but some just use
> a hard coded string. Packages such as diminish, delight and
> dim exist to help customize these.
>
> The define-minor-mode macro creates keymaps and other things
> to help mode authors follow conventions. If it created a
> mode-lighter user option when passed in a string (and not a
> symbol) then users would have an easier time configuring
> their mode-line without having to find and install a package
> to do so.
I think this makes sense -- define-minor-mode would define a
buffer-local variable, I guess, that the users could set to change the
lighter?
Like... `FOO-mode-lighter' or something? Any opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-14 13:40 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 [this message]
[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
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=874l3ou42z.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=30978@debbugs.gnu.org \
--cc=hmelman@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).