From: Lennart Borgman <lennart.borgman@gmail.com>
To: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
Cc: 11513@debbugs.gnu.org
Subject: bug#11513: 24.1.50; raise-frame never raise the foreground window on Windows
Date: Thu, 24 May 2012 18:01:41 +0200 [thread overview]
Message-ID: <CANbX366+NgLHm2PCVyKPUvpJcoT9QXL4N5hDUJmDG=ekpDq_qg@mail.gmail.com> (raw)
In-Reply-To: <20120524060731.184722C037@msa104.auone-net.jp>
On Thu, May 24, 2012 at 8:04 AM, Kazuhiro Ito <kzhr@d1.dion.ne.jp> wrote:
>> > raise-frame always make the unexpected result when Emacs frame is
>> > the foreground window (I mean Emacs frame is colored as active window)
>> > and behind of other application window(s). And, as I described
>> > previously, If Emacs frame is not the foreground window raise-frame
>> > correctly works.
>>
>> But the default behavior on Windows is that a window that is lowered
>> loses its focus. You need to click into it to get focus there. So
>> how come a lowered window still has focus for you?
>
> When I run lower-frame function in Emacs frame interactively, Emacs
> frame is brought behind of other application window(s) but has focus.
> Key inputs are passed to lowered frame. I tested 4 Windows PC, and
> all PCs show the same behavior.
The same happens for me. On the other hand the doc string for
lower-frame does not say that the frame should loose focus.
next prev parent reply other threads:[~2012-05-24 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 21:06 bug#11513: 24.1.50; raise-frame never raise the foreground window on Windows Kazuhiro Ito
2012-05-19 8:02 ` Eli Zaretskii
2012-05-19 12:02 ` Kazuhiro Ito
2012-05-19 12:42 ` Eli Zaretskii
2012-05-19 12:56 ` martin rudalics
2012-05-19 13:47 ` Eli Zaretskii
2012-05-21 19:12 ` Eli Zaretskii
2012-05-23 10:48 ` Kazuhiro Ito
2012-05-23 16:20 ` Eli Zaretskii
2012-05-23 16:38 ` Drew Adams
2012-05-24 6:04 ` Kazuhiro Ito
2012-05-24 16:01 ` Lennart Borgman [this message]
2012-05-28 17:28 ` Eli Zaretskii
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='CANbX366+NgLHm2PCVyKPUvpJcoT9QXL4N5hDUJmDG=ekpDq_qg@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=11513@debbugs.gnu.org \
--cc=kzhr@d1.dion.ne.jp \
/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.