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 22:47:21 +0300 [thread overview]
Message-ID: <83y5oa22ie.fsf@gnu.org> (raw)
In-Reply-To: <4AFBBDB704B34BB18E08E02CE02AD58B@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <rudalics@gmx.at>, <11566@debbugs.gnu.org>
> Date: Tue, 29 May 2012 12:15:51 -0700
>
> > > 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.
>
> No, definitely not with my (non-default) setup. Selecting a frame does not give
> it the input focus.
Not even in "emacs -Q"? IOW, is this an Emacs setup issue, or a
Windows setup issue?
> Hence my need to call `select-frame-set-input-focus' in a few places. And, I
> would guess, hence the existence of two different functions: `select-frame' and
> `s-f-s-i-f'.
My guess is that they exist because on X the situation is quite
different: X defaults (or at least used to) to "pointer to focus", not
"click to focus".
> I'm no expert on any of this, obviously.
Unfortunately, neither am I. I just read a bit about this for the
last few days, because apparently no one else wanted to work on bug
#11513.
next prev parent reply other threads:[~2012-05-29 19:47 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 [this message]
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
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=83y5oa22ie.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 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).