unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 12 Aug 2020 07:31:17 +0000	[thread overview]
Message-ID: <CADbSrJydXUeqnujau8-QCdO4LS_iVAK2p9EyRy7UXZvnbgskaw@mail.gmail.com> (raw)
In-Reply-To: <87ft8txwdk.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

On Tue, Aug 11, 2020 at 11:20 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Allen Li <darkfeline@felesatra.moe> writes:
>
> > 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.
>
> I think we either have to do this, or introduce a formal convention for
> these strings that say either to always add a space to the front or the
> back of them.
>
> I guess we don't really see this much as a problem in practice, because
> we don't have many of these "non-mode" strings in the mode line.
>
> So perhaps settling on a convention and then altering all the instances
> to follow it would be more efficient -- there's probably just a few
> dozen of them?
>

I'm fine with that (I assumed that such a convention already existed
previously on this bug's thread).


>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1837 bytes --]

  reply	other threads:[~2020-08-12  7:31 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
2020-08-11 11:19                 ` Lars Ingebrigtsen
2020-08-12  7:31                   ` Allen Li [this message]
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=CADbSrJydXUeqnujau8-QCdO4LS_iVAK2p9EyRy7UXZvnbgskaw@mail.gmail.com \
    --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).