From: s shaw <skye.shaw@gmail.com>
To: 18164@debbugs.gnu.org
Subject: bug#18164: 24.3.92; appt-mode-line is missing a white-space (in conjunction with display-time-and-date)
Date: Sat, 7 Jan 2017 19:16:14 -0500 [thread overview]
Message-ID: <CACnU8SF06BG1qgOz1nPQJPeVWJtEmdWo=OwVQjuCuHA_G79qfA@mail.gmail.com> (raw)
In-Reply-To: <87ppgkss3c.fsf@vsl28t2g.ww011>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
>> Glenn Morris wrote:
>> ... I could equally well say that display-time-mode-string does not have
>> space at either end.
>> It seems to be a general issue. Eg display-time-mode +
display-battery-mode
>> has the same issue.
> H. Dieter Wilhelm wrote:
> Then this is calling for a general mode-line guide-line ;-). Everything
> textual must be followed by a whitespace.
While not explicitly stated it is implied[1] that a minor mode's lighter
should begin with a space to prevent these issues.
> H. Dieter Wilhelm wrote:
> for the time being, I'll activate then display-time before
app-activate... :-)
Requiring one to load in a particular order or having to reformat
global-mode-string is in some ways contrary to idea behind mode line
control: don't modify mode-line-format, let it delegate the work to its
contents.
Why not just start each of these modes' string with a space?
[1]
https://www.gnu.org/software/emacs/manual/html_node/elisp/Defining-Minor-Modes.html
[-- Attachment #2: Type: text/html, Size: 2783 bytes --]
prev parent reply other threads:[~2017-01-08 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 5:21 bug#18164: 24.3.92; appt-mode-line is missing a white-space (in conjunction with display-time-and-date) H. Dieter Wilhelm
2014-08-02 8:59 ` Glenn Morris
2014-08-02 12:50 ` H. Dieter Wilhelm
2021-08-19 15:49 ` Lars Ingebrigtsen
2021-08-19 20:20 ` H. Dieter Wilhelm
2017-01-08 0:16 ` s shaw [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
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='CACnU8SF06BG1qgOz1nPQJPeVWJtEmdWo=OwVQjuCuHA_G79qfA@mail.gmail.com' \
--to=skye.shaw@gmail.com \
--cc=18164@debbugs.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).