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

Previous Next

Package: emacs;

Reported by: Bruno Félix Rezende Ribeiro <oitofelix <at> gnu.org>

Date: Fri, 31 Oct 2014 15:51:04 UTC

Severity: normal

Found in version 24.4

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: martin rudalics <rudalics <at> gmx.at>
To: Bruno Félix Rezende Ribeiro
 <oitofelix <at> gnu.org>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 18912 <at> debbugs.gnu.org
Subject: Re: bug#18912: 24.4; mode-line corruption on graphical frames in
 dual-headed display
Date: Tue, 04 Nov 2014 08:55:02 +0100
> Here is the result for the *corrupted* frame:
>
>    frame pixel: 756 x 669   cols/lines: 84 x 37   units: 9 x 18
>    frame text pixel: 720 x 667   cols/lines: 80 x 37
>    tool: 36  scroll: 16  fringe: 18  border: 1  right: 0  bottom: 0
>
>    #<window 3 on dev>   parent: nil
>    pixel left: 0   top: 36   size: 754 x 613   new: 0
                                           ^^^
					
This is consistent with what you reported earlier, namely

  Bad configuration (both VGA1 and LVDS1 enabled):

  (window-height) ==> 34
  (window-pixel-height) ==> 613

>    char left: 0   top: 2   size: 83 x 34   new: 0
>    normal: 1.0 x 1.0   new: 0
>    body pixel: 720 x 595   char: 80 x 33
>    width left fringe: 9  left margin: 0  right margin: 0
>    width right fringe: 9  scroll-bar: 16  divider: 0
>    height header-line: 0  mode-line: 18  divider: 0
>
>    #<window 4 on  *Minibuf-0*>   parent: nil
>    pixel left: 0   top: 649   size: 754 x 18   new: 0
>    char left: 0   top: 36   size: 754 x 1   new: 0
>    normal: 1.0 x 1.0   new: 0
>    body pixel: 720 x 18   char: 80 x 1
>    width left fringe: 9  left margin: 0  right margin: 0
>    width right fringe: 9  scroll-bar: 16  divider: 0
>    height header-line: 0  mode-line: 0  divider: 0
>
>
> Here is the result for the *good* frame:
>
>    frame pixel: 756 x 669   cols/lines: 84 x 37   units: 9 x 18
>    frame text pixel: 720 x 667   cols/lines: 80 x 37
>    tool: 36  scroll: 16  fringe: 18  border: 1  right: 0  bottom: 0
>
>    #<window 3 on dev>   parent: nil
>    pixel left: 0   top: 36   size: 754 x 613   new: 0
                                           ^^^

This is not consistent with what you reported earlier, namely

  Good configuration (only VGA1 enabled):

  (window-height) => 34
  (window-pixel-height) => 612

>    char left: 0   top: 2   size: 83 x 34   new: 0
>    normal: 1.0 x 1.0   new: 0
>    body pixel: 720 x 595   char: 80 x 33
>    width left fringe: 9  left margin: 0  right margin: 0
>    width right fringe: 9  scroll-bar: 16  divider: 0
>    height header-line: 0  mode-line: 18  divider: 0
>
>    #<window 4 on  *Minibuf-0*>   parent: nil
>    pixel left: 0   top: 649   size: 754 x 18   new: 0
>    char left: 0   top: 36   size: 754 x 1   new: 0
>    normal: 1.0 x 1.0   new: 0
>    body pixel: 720 x 18   char: 80 x 1
>    width left fringe: 9  left margin: 0  right margin: 0
>    width right fringe: 9  scroll-bar: 16  divider: 0
>    height header-line: 0  mode-line: 0  divider: 0

Can you try getting the results of `window--dump-frame' for these old
(good and bad) configurations, that is with the build you used in your
initial report?  I'd want to see different pixel heights (not 669) for
these two frames but can't tell anything unless the pixel height (612)
of the good window reemerges.

So try first to get the different (window-pixel-height) values back and
then evaluate (window--dump-frame) instead of (window-pixel-height).

Thanks, martin




This bug report was last modified 10 years and 200 days ago.

Previous Next


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