GNU bug report logs - #33498
26.1; Unable to delete minibuffer-only+child frames

Previous Next

Package: emacs;

Reported by: Andreas Politz <politza <at> hochschule-trier.de>

Date: Sun, 25 Nov 2018 11:45:01 UTC

Severity: normal

Tags: fixed

Found in version 26.1

Fixed in version 27.1

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


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

From: martin rudalics <rudalics <at> gmx.at>
To: Andreas Politz <politza <at> hochschule-trier.de>
Cc: 33498 <at> debbugs.gnu.org
Subject: Re: bug#33498: 26.1; Unable to delete minibuffer-only+child frames
Date: Sun, 25 Nov 2018 19:57:16 +0100
> Are you talking about a different feature here ? Because, this is what I
> understand `keep-ratio' is supposed to be doing.

'keep-ratio' simply correlates the sizes of a child and its parent
frame.  If you make a parent frame half its size, 'keep-ratio' makes
its child frames half their size as well.  What I mean is the usual
expanding/shrinking of the minibuffer window you can observe on a
normal minibuffer equipped frame.  For example, via (message"\n\n").

> So, you are saying it's supposed to be like that ?

Yes.

> Them, I don't see a
> reason, why Emacs should disallow deleting the minibuffer-frame as a
> child-frame in this case.

For internal reasons each live frame must have a minibuffer window.
This is hardcoded in a couple of internal routines and if you remove
that restriction (it's the "Attempt to delete a surrogate minibuffer
frame" in frame.c) Emacs will crash soon after that.  Note that a
child frame minibuffer is handled like a normal minibuffer-only frame
in this regard.

martin




This bug report was last modified 6 years and 89 days ago.

Previous Next


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