GNU bug report logs -
#26537
Problems with Emacs frame (GTK)
Previous Next
Full log
Message #29 received at 26537 <at> debbugs.gnu.org (full text, mbox):
Il 17/04/2017 17:43, martin rudalics ha scritto:
>
> (1) Create an initial frame without any desktop involvement. This
> should be the frame from screen-no-desktop.png. I would need the
> dump for that frame (from a 20170327 build) first. And, if it is
> different, a dump of that frame just before you save the desktop. I
> suppose the screen-with-desktop-OK dump above then would stem from a
> new session using a desktop equivalent to the one saved here. Is
> that assumption correct?
From 20170327 build WITHOUT desktop file:
frame pixel: 1020 x 882 cols/lines: 114 x 49 units: 9 x 18
frame text pixel: 990 x 882 cols/lines: 110 x 49
tool: 0 scroll: 14/0 fringe: 16 border: 0 right: 0 bottom: 0
#<window 5> parent: nil
pixel left: 0 top: 0 size: 1020 x 864 new: 864
char left: 0 top: 0 size: 113 x 48 new: 48
normal: 1.0 x 1.0 new: nil
#<window 3 on *scratch*> parent: #<window 5>
pixel left: 0 top: 0 size: 648 x 864 new: 864
char left: 0 top: 0 size: 72 x 48 new: 48
normal: 0.636 x 1.0 new: nil
body pixel: 618 x 846 char: 68 x 47
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 18 divider: 0
#<window 6 on *SPEEDBAR*> parent: #<window 5>
pixel left: 648 top: 0 size: 372 x 864 new: 864
char left: 72 top: 0 size: 41 x 48 new: 48
normal: 0.364 x 1.0 new: nil
body pixel: 342 x 846 char: 38 x 47
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 18 divider: 0
#<window 4 on *Minibuf-0*> parent: nil
pixel left: 0 top: 864 size: 1020 x 18 new: 0
char left: 0 top: 48 size: 113 x 1 new: 1
normal: 1.0 x 1.0 new: 0
body pixel: 990 x 18 char: 110 x 1
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 0 divider: 0
>
> (2) Next you would have to repeat step (1) for the 20170416 build with
> `x-gtk-use-window-move' at its default t.
From 20170416 build WITHOUT desktop file
frame pixel: 1020 x 882 cols/lines: 114 x 49 units: 9 x 18
frame text pixel: 990 x 882 cols/lines: 110 x 49
tool: 0 scroll: 14/0 fringe: 16 border: 0 right: 0 bottom: 0
#<window 5> parent: nil
pixel left: 0 top: 0 size: 1020 x 864 new: 864
char left: 0 top: 0 size: 113 x 48 new: 48
normal: 1.0 x 1.0 new: nil
#<window 3 on *scratch*> parent: #<window 5>
pixel left: 0 top: 0 size: 648 x 864 new: 864
char left: 0 top: 0 size: 72 x 48 new: 48
normal: 0.636 x 1.0 new: nil
body pixel: 618 x 846 char: 68 x 47
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 18 divider: 0
#<window 6 on *SPEEDBAR*> parent: #<window 5>
pixel left: 648 top: 0 size: 372 x 864 new: 864
char left: 72 top: 0 size: 41 x 48 new: 48
normal: 0.364 x 1.0 new: nil
body pixel: 342 x 846 char: 38 x 47
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 18 divider: 0
#<window 4 on *Minibuf-0*> parent: nil
pixel left: 0 top: 864 size: 1020 x 18 new: 0
char left: 0 top: 48 size: 113 x 1 new: 1
normal: 1.0 x 1.0 new: 0
body pixel: 990 x 18 char: 110 x 1
width left fringe: 8 left margin: 0 right margin: 0
width right fringe: 8 scroll-bar: 14 divider: 0
height header-line: 0 mode-line: 0 divider: 0
>
> If, as you said before, the behavior on Windows deviates from the one
> observed here, it would be instructive to see the corresponding frame
> dumps for the Windows build as well.
Yes, on Windows things are different.. see next post
Angelo
This bug report was last modified 8 years and 35 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.