all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11566@debbugs.gnu.org
Subject: bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame?
Date: Tue, 29 May 2012 11:43:00 +0200	[thread overview]
Message-ID: <4FC49A24.7000403@gmx.at> (raw)
In-Reply-To: <8D43F91B0096402A9BCA59FE13513358@us.oracle.com>

 >> IIUC `read-from-minibuffer' uses `redirect-frame-focus' to send the
 >> keystrokes to the minibuffer window.  If that function works
 >> for you in general, we likely have a race condition in this special case.
 >
 > If so, what could a solution/fix be for it?

You didn't tell us whether it works for you "in general".  If you work
with two frames for "some time" does `redirect-frame-focus' what it is
supposed to do?  If it doesn't we have a strange situation where, citing
from Ito's comment in bug#11513,

 > > 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 and OTOH doesn't pass key input to another frame even if
explicitly asked to do so.

 >>  > 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.

 >> Try the sit-for approach.  Try to make a standalone example like
 >> (let ((old-frame ... some existing frame))
 >>    (make-frame)
 >>    (redirect-frame-focus old-frame))
 >> and see whether it fails giving focus to `old-frame'.
 >
 > Still not sure what you mean by using `sit-for' (how/where?).  But I tried that
 > simple example, and yes, it systematically fails to give focus to `old-frame'.
 > The newly created frame keeps the focus - every time.

I suppose my example was just silly.  Maybe you should try again with

(let ((old-frame (selected-frame))
       (new-frame (make-frame)))
   (redirect-frame-focus new-frame old-frame))

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.

martin





  reply	other threads:[~2012-05-29  9:43 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 [this message]
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
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=4FC49A24.7000403@gmx.at \
    --to=rudalics@gmx.at \
    --cc=11566@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.