GNU bug report logs -
#17046
24.3.50; On startup emacs frame has no minibuffer or windows decorations
Previous Next
Reported by: Robert Marshall <robert <at> capuchin.co.uk>
Date: Thu, 20 Mar 2014 09:09:02 UTC
Severity: important
Found in version 24.3.50
Fixed in version 24.4
Done: Juanma Barranquero <lekktu <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #20 received at 17046 <at> debbugs.gnu.org (full text, mbox):
> frame pixel: 992 x 648 cols/lines: 124 x 36 units: 8 x 18
> frame text pixel: 960 x 648 cols/lines: 120 x 36
> tool: 0 scroll: 16 fringe: 16 border: 0 right: 0 bottom: 0
>
> #<window 3 on .emacs> parent: nil
> pixel left: 0 top: 0 size: 992 x 630 new: 561
> char left: 0 top: 0 size: 124 x 35 new: 34
> normal: 1.0 x 1.0 new: ignore
> body pixel: 960 x 612 char: 120 x 34
> width left fringe: 8 left margin: 0 right margin: 0
> width right fringe: 8 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: 630 size: 992 x 18 new: 0
> char left: 0 top: 35 size: 992 x 1 new: 0
> normal: 1.0 x 1.0 new: 0
> body pixel: 960 x 18 char: 120 x 1
> width left fringe: 8 left margin: 0 right margin: 0
> width right fringe: 8 scroll-bar: 16 divider: 0
> height header-line: 0 mode-line: 0 divider: 0
Thanks. According to that dump you should see the minibuffer. What
does evaluating
M-: (frame-parameter nil 'minibuffer)
give? The fact that no title bar is visible is even more strange. Do
you see menu bar and scroll bar normally? Post your screenshot, it's
simpler than telling details. And what happens when you maximize the
frame and restore its normal size immediately afterwards?
martin
This bug report was last modified 11 years and 62 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.