GNU bug report logs - #17046
24.3.50; On startup emacs frame has no minibuffer or windows decorations

Previous Next

Full log

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

From: Robert Marshall <robert <at> capuchin.co.uk>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: martin rudalics <rudalics <at> gmx.at>, 17046 <at> debbugs.gnu.org
Subject: Re: bug#17046: 24.3.50; On startup emacs frame has no minibuffer or
 windows decorations
Date: Tue, 25 Mar 2014 11:09:40 +0000

Juanma Barranquero writes:
 > On Tue, Mar 25, 2014 at 8:12 AM, Robert Marshall <robert <at> capuchin.co.uk> wrote:
 > 
 > > No bug with that line commented
 > 
 > That's great news! Sort of... :-(
 > 
 > That line's here because on some systems (Windows, among others),
 > 
 >   (make-frame '((height . X)))
 > 
 > and
 > 
 >   (modify-frame-parameters (make-frame) '((height . X)))
 > 
 > do not give frames of the same height (that's bug#14795).
 > 
 > Apparently, in your system, modifying a frame size with
 > (tool-bar-lines . 0) triggers a window manager (or Emacs redisplay)
 > bug.
 > 
 > If you evaluate this in emacs -Q, does it fail too?
 > 
 > (let* ((default-frame-alist nil)
 >        (frame (make-frame '((width . 80) (height . 20))))
 >        (tool-bar-lines (frame-parameter frame 'tool-bar-lines)))
 >   (discard-input)
 >   (read-event nil nil 2)
 >   (modify-frame-parameters frame '((tool-bar-lines . 0) (width . 60)
 > (height . 25)))
 >   (modify-frame-parameters frame `((tool-bar-lines . ,tool-bar-lines))))
 > 

It doesn't cause the bug but if I drop those lines into a file and
load it from a -Q -l command line I then see the bug.

Sometimes when I run that elisp (from *scratch*) I see the frame come
up 80 width and it doesn't resize to 60 which seems odd (to me)

R
-- 
Robert Marshall

Previous Next

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