GNU bug report logs - #18912
24.4; mode-line corruption on graphical frames in dual-headed display

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bruno Félix Rezende Ribeiro <oitofelix <at> gnu.org>
Cc: rudalics <at> gmx.at, 18912 <at> debbugs.gnu.org
Subject: Re: bug#18912: 24.4;
 mode-line corruption on graphical frames in dual-headed display
Date: Mon, 03 Nov 2014 22:24:57 +0200

> Date: Mon, 03 Nov 2014 18:06:28 -0200
> From: Bruno Félix Rezende Ribeiro <oitofelix <at> gnu.org>
> CC: rudalics <at> gmx.at, 18912 <at> debbugs.gnu.org
> 
> The outputs of the 'dump-glyph-matrix' command for both the good and bad
> configurations are in the attached files 'dump-glyph-matrix-good.txt'
> and 'dump-glyph-matrix-bad.txt', respectively; they are identical, though.

So you are saying that this last line:

   33: (1) '  lrwxrwxrwx   1 root root          25 Out 30 22:17 initctl -> /run/systemd/init'

which appears in both the "good" and the "bad" dumps, is nevertheless
displayed (overwrites the mode line) only in the "bad" configuration,
and is not visible at all in the "good" one, is that right?

> For the sake of precision I used the method suggested by Martin:
> evaluating the expression
> 
> (while (y-or-n-p "decrease?")
>   (set-frame-height nil (1- (frame-text-height)) nil t))
> 
> in the requested condition.  In order to not be fooled by a spurious
> mode-line redrawing, I killed the buffer and invoked 'C-x d /dev RET'
> again and the glitch was gone, after one iteration (minus 1 pixel).

So hereby you have your workaround already, for free: just make the
frame one pixel lower.

Previous Next

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