unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 33498@debbugs.gnu.org
Subject: bug#33498: 26.1; Unable to delete minibuffer-only+child frames
Date: Sun, 25 Nov 2018 19:57:16 +0100	[thread overview]
Message-ID: <5BFAF08C.6080500@gmx.at> (raw)
In-Reply-To: <87h8g5ggft.fsf@hochschule-trier.de>

 > 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





  reply	other threads:[~2018-11-25 18:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 11:43 bug#33498: 26.1; Unable to delete minibuffer-only+child frames Andreas Politz
2018-11-25 17:40 ` martin rudalics
2018-11-25 18:28   ` Andreas Politz
2018-11-25 18:57     ` martin rudalics [this message]
2018-11-25 19:33       ` Andreas Politz
2018-11-26  9:31         ` martin rudalics
2018-11-26 18:59           ` Andreas Politz
2018-11-27 10:14             ` martin rudalics
2019-03-05 10:12 ` martin rudalics
2019-03-13 20:24   ` Andreas Politz
2019-04-23  8:46     ` martin rudalics
2019-03-06 19:07 ` Paul Eggert
2019-03-07  8:28   ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5BFAF08C.6080500@gmx.at \
    --to=rudalics@gmx.at \
    --cc=33498@debbugs.gnu.org \
    --cc=politza@hochschule-trier.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).