From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Reitter <david.reitter@gmail.com>
Cc: 3302@emacsbugs.donarmstrong.com
Subject: bug#3302: Frame deletion with 'force fails
Date: Sun, 17 May 2009 23:51:16 -0400 [thread overview]
Message-ID: <jwvoctr2hza.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <66CADE2D-3FA6-4467-BA39-AB7BC0DF6767@gmail.com> (David Reitter's message of "Sun, 17 May 2009 22:41:43 -0400")
> After all, the menu bar may still be visible (doesn't need a frame).
Oh, I see. Yes, under NS it might make sense.
> I looked some more at the code (mainly by enabling frame deletion in this
> case), and because we expect there to be a selected frame pretty much at
> all times, I don't think this can be fixed. (But I would hope I'm wrong.)
It's easy to fix: just provide some special frame for it (one that
isn't displayed).
> Does Emacs in daemon mode run with a special event loop?
No. But it has a special terminal (to a large extent, the same as used
for --batch mode), so it does have a "selected-frame".
> I'd be happy for this to be closed as a "wontfix" bug, or if the
> delete-frame doc string was improved.
I'm not opposed to installing NS-specific changes to address this
problem, but they will need to be made elsewhere since, as you've
noticed, too much of the code relies on the existence of
a selected-frame.
Stefan
next prev parent reply other threads:[~2009-05-18 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 4:07 bug#3302: closing this David Reitter
2009-05-16 0:48 ` bug#3302: Frame deletion with 'force fails David Reitter
2009-05-17 20:31 ` Stefan Monnier
2009-05-18 2:41 ` David Reitter
2009-05-18 3:51 ` Stefan Monnier [this message]
2009-05-18 3:58 ` David Reitter
2009-05-22 4:15 ` bug#3302: marked as done (Frame deletion with 'force fails) Emacs bug Tracking System
2009-05-22 4:58 ` bug#3302: closing this Jason Rumney
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=jwvoctr2hza.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3302@emacsbugs.donarmstrong.com \
--cc=david.reitter@gmail.com \
/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.