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

Previous Next

Package: emacs;

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 #116 received at 17046 <at> debbugs.gnu.org (full text, mbox):

From: Juanma Barranquero <lekktu <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 17046 <at> debbugs.gnu.org, Robert Marshall <robert <at> capuchin.co.uk>
Subject: Re: bug#17046: 24.3.50; On startup emacs frame has no minibuffer or
 windows decorations
Date: Sat, 22 Mar 2014 15:33:26 +0100
On Sat, Mar 22, 2014 at 3:20 PM, martin rudalics <rudalics <at> gmx.at> wrote:

> One more question: Is there a way to have frameset make all changes only
> with a strictly visible frame

Please clarify. Do you mean:

- Not to restore upon a non-strictly visible frame (and so choose
another or create a new one)?
- To wait until the frame is visible?

(I'm not sure what do you mean with "strictly visible", BTW).

The :reuse-frames arg of `frameset-restore' accepts a predicate, so if
you have a way to decide from Elisp that a frame is "strictly
visible", you can allow or disallow its reusing.

   J




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.