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:46:56 +0300 [thread overview]
Message-ID: <83zk8r0wan.fsf@gnu.org> (raw)
In-Reply-To: <A2ED23C80C624D67AA1D7A96FBDDCFA8@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <11566@debbugs.gnu.org>
> Date: Tue, 29 May 2012 09:10:12 -0700
>
> > 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.
>
> Got it. I too was using "foreground" to mean the topmost (highest in the
> stacking order), and not the frame that receives keyboard input.
Well, it's tricky terminology to be sure.
> > The problem in bug #11513 was that a frame that was already a
> > foreground frame was not raised. Maybe something similar happens
> > here.
>
> Dunno. I don't have a lot of hope that it's related. But who knows?
One can hope.
However, in the interests of clarity, could you please describe the
bug again, in terms of which frame has focus (i.e. is the "foreground"
window), which is at the top of Z-order, and which has its border
highlighted, after read-from-minibuffer is called, as you described in
your original report?
next prev parent reply other threads:[~2012-05-29 16:46 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
2012-05-29 16:10 ` Drew Adams
2012-05-29 16:46 ` Eli Zaretskii [this message]
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=83zk8r0wan.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.