From: Allen Li <vianchielfaura@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30056@debbugs.gnu.org
Subject: bug#30056: 25.3; battery-mode-line-string missing leading space
Date: Fri, 12 Jan 2018 00:18:21 -0800 [thread overview]
Message-ID: <CAJr1M6ck1nD=f4-KiMH2dhG3ErpTR35uE+ejF2u_=S+5QrVS_A@mail.gmail.com> (raw)
In-Reply-To: <83mv1k4cd1.fsf@gnu.org>
Interestingly, when display-battery-mode and display-time-mode are set
through my custom file, the battery display comes before the time
display. However, toggling either of them interactively will always
result in the time display coming before the battery display.
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.
next prev parent reply other threads:[~2018-01-12 8:18 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 [this message]
2020-08-10 13:43 ` Lars Ingebrigtsen
2020-08-11 8:40 ` Allen Li
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='CAJr1M6ck1nD=f4-KiMH2dhG3ErpTR35uE+ejF2u_=S+5QrVS_A@mail.gmail.com' \
--to=vianchielfaura@gmail.com \
--cc=30056@debbugs.gnu.org \
--cc=eliz@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).