From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: contovob@tcd.ie, 34476@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#34476: fluffy whitespace in the mode-line, despite it running off the screen
Date: Fri, 07 Aug 2020 16:52:48 +0300 [thread overview]
Message-ID: <83sgcy7ebz.fsf@gnu.org> (raw)
In-Reply-To: <87mu367iue.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 07 Aug 2020 14:15:21 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: contovob@tcd.ie, 34476@debbugs.gnu.org, jidanni@jidanni.org
> Date: Fri, 07 Aug 2020 14:15:21 +0200
>
> So nothing is displayed until that call to display_string, in my reading
> of the code.
Nitpicking: display_string doesn't display anything, it just prepares
glyph structures used by other code to actually display the mode line
on the glass.
> OK, I've now done some more testing -- I removed my call to
> display_string, and no mode line is displayed at all, which kinda
> supports my reading of the code?
I don't want to argue with your reading of the code. I'm saying that
the natural way of removing extra spaces is to post-process the glyphs
produced by display_string directly; anything else is IMO inelegant
and unnatural.
next prev parent reply other threads:[~2020-08-07 13:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:34 bug#34476: fluffy whitespace in the mode-line, despite it running off the screen 積丹尼 Dan Jacobson
2019-07-09 16:43 ` Lars Ingebrigtsen
2019-07-09 20:46 ` Basil L. Contovounesios
2019-07-09 21:44 ` Lars Ingebrigtsen
2020-08-07 8:00 ` Lars Ingebrigtsen
2020-08-07 8:31 ` Lars Ingebrigtsen
2020-08-07 11:32 ` Eli Zaretskii
2020-08-07 11:41 ` Lars Ingebrigtsen
2020-08-07 11:59 ` Eli Zaretskii
2020-08-07 12:15 ` Lars Ingebrigtsen
2020-08-07 13:52 ` Eli Zaretskii [this message]
2020-08-08 9:11 ` Lars Ingebrigtsen
2020-08-08 9:48 ` Eli Zaretskii
2020-08-08 10:01 ` Eli Zaretskii
2020-08-08 11:18 ` Lars Ingebrigtsen
2020-08-08 12:55 ` Eli Zaretskii
2020-08-08 14:16 ` Lars Ingebrigtsen
2020-08-08 15:00 ` Eli Zaretskii
2020-08-09 9:56 ` Lars Ingebrigtsen
2020-08-09 14:07 ` Eli Zaretskii
2020-08-10 14:46 ` Eli Zaretskii
2020-08-10 14:56 ` Lars Ingebrigtsen
2020-08-14 10:46 ` Eli Zaretskii
2020-08-14 12:00 ` Lars Ingebrigtsen
2020-08-14 13:16 ` Eli Zaretskii
2020-08-15 8:47 ` Eli Zaretskii
2020-08-15 10:55 ` Lars Ingebrigtsen
2020-08-15 15:12 ` Eli Zaretskii
2020-08-16 11:21 ` Lars Ingebrigtsen
2020-08-16 14:43 ` Eli Zaretskii
2020-08-17 8:33 ` Lars Ingebrigtsen
2020-08-17 14:17 ` Eli Zaretskii
2020-12-29 3:54 ` Lars Ingebrigtsen
2020-12-29 15:02 ` Eli Zaretskii
2020-12-29 15:07 ` Lars Ingebrigtsen
2020-12-29 15:54 ` Eli Zaretskii
2020-12-29 17:04 ` martin rudalics
2020-12-30 2:36 ` Lars Ingebrigtsen
2020-08-08 11:18 ` Lars Ingebrigtsen
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=83sgcy7ebz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34476@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=jidanni@jidanni.org \
--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).