From: Allen Li <darkfeline@felesatra.moe>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 30056@debbugs.gnu.org
Subject: bug#30056: 25.3; battery-mode-line-string missing leading space
Date: Tue, 11 Aug 2020 01:40:40 -0700 [thread overview]
Message-ID: <80ft8t8tiv.fsf@felesatra.moe> (raw)
In-Reply-To: <87tuxa39c7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 10 Aug 2020 15:43:20 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Allen Li <vianchielfaura@gmail.com> writes:
>
>> The cause of this odd behavior is that display-battery-mode appends
>> and removes its symbol in global-mode-string when it is toggled on or
>> off, while display-time-mode only appends its symbol and does not
>> remove it when it is toggled off. The reason display-battery-mode
>> comes first after Emacs starts is because of how the custom file
>> works; user options are sorted alphabetically and display-battery-mode
>> comes first, so it is appended first.
>>
>> Naturally, this has some implications for whether each display uses
>> leading, trailing, or no space.
>
> Indeed. Just a random idea: Would it make sense to add a mode line
> construct like "%S" to mode-line-format that means "put a space here if
> there isn't one already"? Then battery could put "%S<current string"
> into the list?
>
> Would that work?
I find that idea intriguing. It would work, and it's a useful feature
to have as an Emacs Lisp developer, because it provide a robust solution
to the problem of "I want to have a space separation in the mode line,
but I don't know what comes before/after me".
Although personally, I feel a little dirty adding a new %-construct just
for this.
next prev parent reply other threads:[~2020-08-11 8:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 3:26 bug#30056: 25.3; battery-mode-line-string missing leading space Allen Li
2018-01-10 8:45 ` bug#30056: [PATCH] Add leading space to battery-mode-line-format Allen Li
2018-01-10 15:29 ` bug#30056: 25.3; battery-mode-line-string missing leading space Eli Zaretskii
2018-01-10 17:06 ` Glenn Morris
2018-01-10 19:05 ` Eli Zaretskii
2018-01-10 23:26 ` Allen Li
2018-01-11 15:57 ` Eli Zaretskii
2018-01-12 8:18 ` Allen Li
2020-08-10 13:43 ` Lars Ingebrigtsen
2020-08-11 8:40 ` Allen Li [this message]
2020-08-11 11:19 ` Lars Ingebrigtsen
2020-08-12 7:31 ` Allen Li
2021-07-22 14:15 ` Lars Ingebrigtsen
2021-07-23 12:48 ` Lars Ingebrigtsen
2021-07-23 18:23 ` Juri Linkov
2021-07-24 11:54 ` Lars Ingebrigtsen
2021-07-26 23:09 ` Juri Linkov
2021-07-27 20:56 ` Juri Linkov
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=80ft8t8tiv.fsf@felesatra.moe \
--to=darkfeline@felesatra.moe \
--cc=30056@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@gnu.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).