From: Lennart Borgman <lennart.borgman@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>,
Stefan Monnier <monnier@iro.umontreal.ca>,
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Frame ordering
Date: Mon, 14 Jun 2010 19:19:12 +0200 [thread overview]
Message-ID: <AANLkTikfK_cWJ3lp1OiTpVWkcHscuoo84UA3dbZXV_bG@mail.gmail.com> (raw)
In-Reply-To: <268FB0C3-89E6-41DF-9136-4968332547FA@gmail.com>
On Mon, Jun 14, 2010 at 7:14 PM, David Reitter <david.reitter@gmail.com> wrote:
> On Jun 14, 2010, at 12:47 PM, Lennart Borgman wrote:
>>
>> Was not what you shown (Command-Tab switching) what the window handler
>> on OS X does? If so then trying to interfere with that is probably a
>> bad idea (and is prevented actively by at least w32).
>
> To clarify: I spoke about application switching, not switching between the windows of a single application (A-` and A-~).
> OSX and Windows follow different philosophies there.
>
> I fully agree that one should let the window manager do it, but we want to make sure that this interacts nicely with programmatically raised frames and such. I think this should be no problem.
I see, then we misunderstood each other.
Perhaps one of the main problem with getting this to work with
programmatically raised windows is that it is sometimes hard to wait
for the relevant message from the window manager before proceeding. I
think that is necessary.
next prev parent reply other threads:[~2010-06-14 17:19 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
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 [this message]
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=AANLkTikfK_cWJ3lp1OiTpVWkcHscuoo84UA3dbZXV_bG@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--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).