From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52183@debbugs.gnu.org, dm@mssdvd.com
Subject: bug#52183: 29.0.50; Empty space in the mode line if server-mode is active
Date: Sat, 04 Dec 2021 21:36:43 +0200 [thread overview]
Message-ID: <83czmc5fhw.fsf@gnu.org> (raw)
In-Reply-To: <875ys46vjf.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 04 Dec 2021 20:04:52 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: dm@mssdvd.com, 52183@debbugs.gnu.org
> Date: Sat, 04 Dec 2021 20:04:52 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Bottom line: I think to make this work as intended, bindings.el should
> > be modified to produce a Lisp string from all those 4 elements, by
> > concatenating them, and then the min-width display spec should be put
> > on the result of the concatenation.
>
> I thought we were going to fix min-width so that that machinery was also
> called on the C strings (that are going to end up having the text
> property added afterwards)?
I still plan on doing that, but I don't see how it would help here.
AFAIU, it will make the result worse.
The main point of what I wrote is that we actually display the whole
5-to-6 character sequence of indicators as 4 separate strings, not as
a single string made of concatenation of those 4. So even if/when the
min-width stuff is fixed as we discussed, you will have 4 strings
displayed one after the other, and each one of them has the min-width
spec, so each one of them will be displayed as at least 5 characters.
And that's not what you want here.
next prev parent reply other threads:[~2021-12-04 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 15:59 bug#52183: 29.0.50; Empty space in the mode line if server-mode is active Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 8:57 ` bug#52183: (29.0.50; Empty space in the mode line if server-mode is active) Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 16:52 ` Eli Zaretskii
2021-11-30 17:52 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 18:30 ` Eli Zaretskii
2021-12-04 9:35 ` bug#52183: 29.0.50; Empty space in the mode line if server-mode is active Eli Zaretskii
2021-12-04 9:56 ` Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-04 10:29 ` Eli Zaretskii
2021-12-04 11:59 ` Eli Zaretskii
2021-12-04 19:04 ` Lars Ingebrigtsen
2021-12-04 19:36 ` Eli Zaretskii [this message]
2021-12-04 22:01 ` Lars Ingebrigtsen
2021-12-05 6:59 ` Eli Zaretskii
2021-12-05 20:04 ` Lars Ingebrigtsen
[not found] ` <handler.52183.B.163820159613081.ack@debbugs.gnu.org>
2023-07-28 14:43 ` bug#52183: Acknowledgement (29.0.50; Empty space in the mode line if server-mode is active) Davide Masserut via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-29 11:22 ` Eli Zaretskii
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=83czmc5fhw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52183@debbugs.gnu.org \
--cc=dm@mssdvd.com \
--cc=larsi@gnus.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).