From: Andreas Politz <politza@hochschule-trier.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 33498@debbugs.gnu.org
Subject: bug#33498: 26.1; Unable to delete minibuffer-only+child frames
Date: Sun, 25 Nov 2018 20:33:06 +0100 [thread overview]
Message-ID: <87d0qtgdfx.fsf@hochschule-trier.de> (raw)
In-Reply-To: <5BFAF08C.6080500@gmx.at> (martin rudalics's message of "Sun, 25 Nov 2018 19:57:16 +0100")
martin rudalics <rudalics@gmx.at> writes:
> [...] 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").
I see.
> 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) [...]
I don't mean to remove that restriction. But in this case, where the
parent is deleted and the child is the parent's minibuffer-frame (and
there are no other frame using this minibuffer-frame) this restriction
doesn't seem to apply, at least on a conceptual level.
From the point of a user, this means that he either needs to advise
`delete-frame' or use a different command in order to delete these kinds
of frames.
Andreas
next prev parent reply other threads:[~2018-11-25 19:33 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
2018-11-25 19:33 ` Andreas Politz [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0qtgdfx.fsf@hochschule-trier.de \
--to=politza@hochschule-trier.de \
--cc=33498@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.