From: "Drew Adams" <drew.adams@oracle.com>
To: <11566@debbugs.gnu.org>
Subject: bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame?
Date: Mon, 28 May 2012 11:02:44 -0700 [thread overview]
Message-ID: <D1210F9557B246B58CEBAB475DBA238E@us.oracle.com> (raw)
In-Reply-To: <6A40227DCFBF427491B710A473E45744@us.oracle.com>
> Here is a workaround I've come up with when trying to "fix" `r-f-m'
> itself:
>
> (defadvice read-from-minibuffer (around
> focus-standalone-minibuf activate)
> "..."
> (let ((selframe (selected-frame))
> result)
> (unwind-protect
> (progn (when (and (boundp '1on1-minibuffer-frame)
> (frame-live-p 1on1-minibuffer-frame))
> (select-frame-set-input-focus
> 1on1-minibuffer-frame))
> (setq result ad-do-it))
> (ignore-errors (select-frame-set-input-focus selframe))
> result)))
FYI - Not sure why (haven't looked), but that defadvice makes it impossible to
see any messages in the minibuffer. I need to open *Messages* to see any
messages. So such an approach is definitely not sufficient.
next prev parent reply other threads:[~2012-05-28 18:02 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
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 [this message]
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=D1210F9557B246B58CEBAB475DBA238E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=11566@debbugs.gnu.org \
/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.