From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: David Reitter <david.reitter@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Frame ordering
Date: Mon, 14 Jun 2010 12:30:51 +0900 [thread overview]
Message-ID: <wly6eiguj8.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <1F24A2FE-EF86-4E03-84CF-69748A482C64@gmail.com>
>>>>> On Sun, 13 Jun 2010 22:42:40 -0400, David Reitter <david.reitter@gmail.com> said:
> On Jun 13, 2010, at 8:30 PM, Stefan Monnier wrote:
>>> Should Vframe_list not be updated in the event loop?
>>
>> Why not update it in Fselect_frame, and obey the `norecord'
>> argument?
> Tried that - doesn't catch clicks into the frame by the user.
> However, I got the code below to work at the end of do_switch_frame.
> I think this would be a substantial, and good change to the way
> frames are ordered. Are you OK with this?
Did you confirm that the original problem was not specific to the NS
port?
We usually don't need to specify the next focus window (in
window-system terminology) that is to be selected when a window is
closed. The window system or the window manager automatically move
the focus according to its policy (e.g., the frontmost window, which
may belong to another application). This also applies to Cocoa
AppKit.
http://lists.gnu.org/archive/html/bug-gnu-emacs/2009-05/msg00373.html
http://lists.gnu.org/archive/html/bug-gnu-emacs/2009-05/msg00413.html
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2010-06-14 3:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E9FAA849-1E93-4DD7-AE9D-5E644D990202@univie.ac.at>
2010-06-11 12:29 ` Frame ordering David Reitter
2010-06-11 13:22 ` martin rudalics
2010-06-11 13:55 ` David Reitter
2010-06-11 17:13 ` martin rudalics
2010-06-11 21:04 ` David Reitter
2010-06-12 8:01 ` martin rudalics
2010-06-13 20:16 ` David Reitter
2010-06-14 0:30 ` Stefan Monnier
2010-06-14 2:42 ` David Reitter
2010-06-14 3:30 ` YAMAMOTO Mitsuharu [this message]
2010-06-14 6:50 ` martin rudalics
2010-06-14 6:55 ` Lennart Borgman
2010-06-14 7:35 ` YAMAMOTO Mitsuharu
2010-06-14 8:24 ` martin rudalics
2010-06-14 8:31 ` YAMAMOTO Mitsuharu
2010-06-14 9:20 ` martin rudalics
2010-06-14 9:28 ` YAMAMOTO Mitsuharu
2010-06-14 13:29 ` Stefan Monnier
2010-06-14 3:52 ` YAMAMOTO Mitsuharu
2010-06-14 15:52 ` David Reitter
2010-06-14 16:05 ` Lennart Borgman
2010-06-14 16:29 ` David Reitter
2010-06-14 16:47 ` Lennart Borgman
2010-06-14 17:10 ` Jan Djärv
2010-06-14 17:15 ` Lennart Borgman
2010-06-14 17:14 ` David Reitter
2010-06-14 17:19 ` Lennart Borgman
2010-06-14 18:49 ` Stefan Monnier
2010-06-15 3:54 ` David Reitter
2010-06-15 13:25 ` Stefan Monnier
2010-06-15 14:33 ` David Reitter
2010-06-15 9:24 ` YAMAMOTO Mitsuharu
2010-06-14 6:50 ` martin rudalics
2010-06-12 4:12 ` David Reitter
2010-06-12 5:42 ` YAMAMOTO Mitsuharu
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=wly6eiguj8.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--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 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).