unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Allen Li <vianchielfaura@gmail.com>
Cc: 30056@debbugs.gnu.org
Subject: bug#30056: 25.3; battery-mode-line-string missing leading space
Date: Thu, 11 Jan 2018 17:57:30 +0200	[thread overview]
Message-ID: <83mv1k4cd1.fsf@gnu.org> (raw)
In-Reply-To: <CAJr1M6crW=kvXoYOvytouMGbyihts38ZXVp2_FHi6obh57AoUQ@mail.gmail.com> (message from Allen Li on Wed, 10 Jan 2018 15:26:42 -0800)

> From: Allen Li <vianchielfaura@gmail.com>
> Date: Wed, 10 Jan 2018 15:26:42 -0800
> Cc: Glenn Morris <rgm@gnu.org>, 30056@debbugs.gnu.org
> 
> >> See also https://debbugs.gnu.org/18164
> >
> > We don't do this consistently in the modes which use
> > global-mode-string: some of them leave a blank at the beginning,
> > others (the majority, AFACT) don't.  There's not much space on the
> > mode line, so I'm not sure which way is better.
> 
> The standard for minor mode strings is to include a leading space, right?

That's just it: I'm not sure.

> In any case, Emacs packages should probably be consistent, and
> currently display-battery-mode and display-time-mode are inconsistent.
> I don’t know which other modes use global-mode-string; is display-time
> mode the only outlier?

Not at all: grep for that variable in the Emacs source tree, and you
will see that most of its users don't start their strings with a
blank.  Which is why I asked this question:

> > But if we want to have a separation there, would it make sense to do
> > this in bindings.el, so that global-mode-string is always separated by
> > a blank from the preceding text, and modes don't have to remember this
> > gork?





  reply	other threads:[~2018-01-11 15:57 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 [this message]
2018-01-12  8:18           ` Allen Li
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=83mv1k4cd1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30056@debbugs.gnu.org \
    --cc=vianchielfaura@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).