From: Eli Zaretskii <eliz@gnu.org>
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 19:44:19 +0300 [thread overview]
Message-ID: <831um32azg.fsf@gnu.org> (raw)
In-Reply-To: <9A9A32EAE9D64B438EDA74E1F3F488FE@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <rudalics@gmx.at>, <11566@debbugs.gnu.org>
> Date: Tue, 29 May 2012 09:10:15 -0700
>
> > > > (let ((old-frame (selected-frame))
> > > > (new-frame (make-frame)))
> > > > (redirect-frame-focus new-frame old-frame))
> > >
> > > That puts (keeps) the input focus in old-frame. So it
> > > seems to work as it should.
> >
> > No, it keeps focus in new-frame, but makes it so the input you type at
> > new-frame gets sent to old-frame.
>
> Hm. Maybe I'm unclear about "focus". To me, "focus" was about input focus: the
> focused frame is the one that accepts/receives keyboard input.
Well, yes, but redirect-frame-focus explicitly parts them, AFAIU.
> In something like `select-frame-set-input-focus', my interpretation was that
> frame selection was related to the border highlighting and setting input focus
> was related to receiving keyboard input. AFAIK, `select-frame' does the former,
> but `select-frame-set-input-focus' is needed to get the latter.
On Windows, at least with the default setup, selecting a frame also
grabs focus. So these two functions do the same.
> > Thus, this:
> >
> > > (But new-frame has its title and border highlighted as if
> > > it had the focus. Somehow there is a disconnect between the two.
> >
> > is normal and expected behavior (AFAIU).
>
> Expected from `redirect-frame-focus', I guess you mean.
Yes, of course.
> So IIUC, `select-frame-set-input-focus' does `select-frame' plus
> `redirect-frame-focus'?
No, it just raises the frame after selecting it and makes sure it has
focus (which in most situations it will have by virtue of being
raised).
next prev parent reply other threads:[~2012-05-29 16:44 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 [this message]
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=831um32azg.fsf@gnu.org \
--to=eliz@gnu.org \
--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.