From: Stephen Berman <stephen.berman@gmx.net>
To: 53776@debbugs.gnu.org
Cc: goncholden@protonmail.com
Subject: bug#53776: Modeline indicator when using define-minor-mode
Date: Fri, 04 Feb 2022 14:02:27 +0100 [thread overview]
Message-ID: <87v8xun5ss.fsf@rub.de> (raw)
In-Reply-To: <CF-YW0_yS-IIBhXJmqX2imijIPtnxucxIbY09KOxp8z6hXQJE2kogLFpQiffCguPHFQbE1fXbdvJ6omFbfd7T4lAApbCDsRrSfh4gdeTZFs=@protonmail.com> (goncholden via's message of "Fri, 04 Feb 2022 11:55:45 +0000")
On Fri, 04 Feb 2022 11:55:45 +0000 goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> Have been using define-minor-mode and noticed that when setting the
> modeline indicator, the text is appended with no space between other
> modeline indicators. Is this how :lighter is supposed to work?
Yes, the lack of a space is in the definition of `mode-line-modes':
`(:propertize ("" minor-mode-alist)
I guess the reason is that you can have multiple minor mode lighters and
providing a space between each would complicate the definition of
`mode-line-modes', so that's the job of the minor mode definition
itself:
> (define-minor-mode rich-minor-mode
> "This is the docstring."
> :lighter "rich"
So you should do this: :lighter " rich"
Steve Berman
next prev parent reply other threads:[~2022-02-04 13:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 11:55 bug#53776: Modeline indicator when using define-minor-mode goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 13:02 ` Stephen Berman [this message]
2022-02-04 13:22 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 13:35 ` Stephen Berman
2022-02-04 14:05 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 14:38 ` Stephen Berman
2022-02-04 14:43 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-04 14:49 ` Stephen Berman
2022-02-05 6:45 ` Lars Ingebrigtsen
2022-02-06 3:39 ` Michael Heerdegen
2022-02-06 12:52 ` Stephen Berman
2022-02-06 21:52 ` Michael Heerdegen
2022-02-06 23:13 ` Stephen Berman
2022-02-06 23:59 ` Michael Heerdegen
2022-02-07 0:28 ` Stephen Berman
2022-02-07 0:51 ` Michael Heerdegen
2022-02-07 22:40 ` Stephen Berman
2022-02-06 17:12 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 0:12 ` Phil Sainty
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=87v8xun5ss.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=53776@debbugs.gnu.org \
--cc=goncholden@protonmail.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).