From: Matt McClure <matthewlmcclure@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: delete-frame raises other frames
Date: Sat, 22 Oct 2016 16:38:05 +0000 [thread overview]
Message-ID: <CABUpbWRZucZ5SOLvP1bP6OHru2mRw_xVKRB=FE0Co8HCmksNKQ@mail.gmail.com> (raw)
In-Reply-To: <83k2d5ww1x.fsf@gnu.org>
On Tue, Oct 18, 2016 at 10:50 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Well, this doesn't happen to me, and from lack of other "me too"
> responses, I'm guessing that this is either specific to OS X or even
> to your system's configuration.
>
Thanks, Eli.
My guess is that it's specific to OS X.
I looked at the Emacs source code a bit. I found the following in
delete_frame[1]:
```
#ifdef NS_IMPL_COCOA
else
/* Under NS, there is no system mechanism for choosing a new
window to get focus -- it is left to application code.
So the portion of THIS application interfacing with NS
needs to know about it. We call Fraise_frame, but the
purpose is really to transfer focus. */
Fraise_frame (frame1);
#endif
```
The following might also be relevant:
- Apple's window concepts documentation[2]
- Uses of NSApp[3], e.g.,
- activateIgnoringOtherApps[4]
- makeKeyAndOrderFront[5]
[1]:
https://github.com/emacs-mirror/emacs/blob/d4a32c4d5955ac04c5017a43042d873e42b3ebec/src/frame.c#L1639
[2]:
https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/WinPanel/Concepts/ChangingMainKeyWindow.html
[3]: https://github.com/emacs-mirror/emacs/search?utf8=%E2%9C%93&q=nsapp
[4]:
https://github.com/emacs-mirror/emacs/search?utf8=%E2%9C%93&q=activateIgnoringOtherApps&type=Code
[5]:
https://github.com/emacs-mirror/emacs/search?utf8=%E2%9C%93&q=makeKeyAndOrderFront&type=Code
next prev parent reply other threads:[~2016-10-22 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 18:36 delete-frame raises other frames Matt McClure
2016-10-14 19:08 ` Eli Zaretskii
2016-10-14 23:01 ` Matt McClure
2016-10-18 13:30 ` Matt McClure
2016-10-18 14:50 ` Eli Zaretskii
2016-10-22 16:38 ` Matt McClure [this message]
2016-10-14 19:40 ` Yuri Khan
2016-10-14 23:02 ` Matt McClure
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='CABUpbWRZucZ5SOLvP1bP6OHru2mRw_xVKRB=FE0Co8HCmksNKQ@mail.gmail.com' \
--to=matthewlmcclure@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).