GNU bug report logs - #34476
fluffy whitespace in the mode-line, despite it running off the screen

Previous Next

Full log

Message #59 received at 34476 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: contovob <at> tcd.ie, 34476 <at> debbugs.gnu.org
Subject: Re: bug#34476: fluffy whitespace in the mode-line, despite it
 running off the screen
Date: Sat, 08 Aug 2020 18:00:23 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: contovob <at> tcd.ie,  34476 <at> debbugs.gnu.org
> Date: Sat, 08 Aug 2020 16:16:04 +0200
> 
> There's four spaces between *scratch* and All because they have
> different faces...  which makes me wonder why there's trailing spaces in
> the buffer name at all, instead of just three spaces after the buffer
> name in the mode line format?

That's because mode-line-buffer-identification uses %12b as the format
to show the buffer name.

> There's also the question of allowing a value of `long' to
> mode-line-compact -- which would only compact the mode line if it's
> longer than the window width.  Would that be difficult to add?

No, it should be an almost trivial addition to the condition under
which we perform the squeezing.  Basically, compare it.current_x with
it.last_visible_x.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.