From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 11566@debbugs.gnu.org
Subject: bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame?
Date: Tue, 29 May 2012 18:40:15 +0300 [thread overview]
Message-ID: <83aa0r2dy8.fsf@gnu.org> (raw)
In-Reply-To: <4FC49A24.7000403@gmx.at>
> Date: Tue, 29 May 2012 11:43:00 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 11566@debbugs.gnu.org
>
> > > 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.
>
> so Windows OT1H handles key input passed to a frame that is not in the
> foreground
Careful with your terminology: at least on MS-Windows, a "foreground"
frame is the frame that has focus and receives input. So what you say
cannot happen by definition.
In the scenario you cited above, the frame is lowered (i.e. brought
behind, or "below" in Z-order, the other frames/windows), but it is
still the foreground frame and therefore it still has focus and
receives keyboard input. So it's unclear to me what exactly is the
problem in the OT1H scenario.
> and OTOH doesn't pass key input to another frame even if
> explicitly asked to do so.
I have just fixed a similar problem in bug #11513. I suggest that
Drew wait until the corresponding binaries are available, and see
whether this problem is solved as well.
The problem in bug #11513 was that a frame that was already a
foreground frame was not raised. Maybe something similar happens
here.
> >> > Shouldn't [`read-from-minibuffer'] have the responsibility
> >> > here to give the minibuffer frame the focus?
> >>
> >> Yes. But the window manager must not intercept it.
> >
> > But that's what seems to be happening (intercept or interrupt or some such).
>
> That's what we have to find out.
I don't think this is what happens here. To raise a frame, Emacs
sends a message with a private code to itself, so I doubt that the
window manager could intercept or interrupt it, even if it wanted to.
> I don't know anything about `redirect-frame-focus' and can't test it
> reliably here because I'm using special autoraise-frame settings which
> likely interfere with any such focus redirection.
According to my reading, it just highlights the frame that had focus
redirected to it.
next prev parent reply other threads:[~2012-05-29 15:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 0:07 bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame? Drew Adams
2012-05-27 13:22 ` martin rudalics
2012-05-27 15:01 ` Drew Adams
2012-05-29 9:43 ` martin rudalics
2012-05-29 14:12 ` Drew Adams
2012-05-29 15:44 ` Eli Zaretskii
2012-05-29 16:10 ` Drew Adams
2012-05-29 16:44 ` Eli Zaretskii
2012-05-29 19:15 ` Drew Adams
2012-05-29 19:47 ` Eli Zaretskii
2012-05-29 20:28 ` Drew Adams
2012-05-29 15:40 ` Eli Zaretskii [this message]
2012-05-29 16:10 ` Drew Adams
2012-05-29 16:46 ` Eli Zaretskii
2012-05-29 19:15 ` Drew Adams
2012-05-29 20:20 ` Eli Zaretskii
2012-05-29 21:31 ` Drew Adams
2012-05-30 18:43 ` Eli Zaretskii
2012-05-30 20:10 ` Drew Adams
2012-05-28 18:02 ` Drew Adams
2012-10-03 9:13 ` martin rudalics
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=83aa0r2dy8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11566@debbugs.gnu.org \
--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 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.