From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: eldoc vs minibuffer-auto-raise
Date: Sat, 19 Jan 2019 14:25:36 -0800 (PST) [thread overview]
Message-ID: <751af5b0-cfe6-4887-8489-0f40b0be0d75@default> (raw)
In-Reply-To: <5C437123.2010504@gmx.at>
> > I'm using MS Windows. Perhaps the window mgr is involved
> > here, switching the focus to the minibuffer frame in your
> > case?
>
> No. I suppose you have set 'w32-grab-focus-on-raise' to nil so you
> won't see this behavior.
Yes, it's nil. (Not that I even remembered what
that variable is or does, or when I set it to nil.)
However, I see the same behavior even if I set the
var to `t'. In my case, no doubt due to something
else in my setup, the focus stays where I left it,
in the *scratch* frame. Eldoc puts its msgs in the
minibuffer frame (in the echo area, presumably), and
focus stays put, in *scratch*.
However2: With the variable = t things are really
annoying outside of Emacs!
E.g., while typing this mail in Outlook (not Emacs),
Eldoc (?) keeps periodically sending the window-mgr
focus to the Emacs *scratch* frame (not to the
minibuffer frame - again, no doubt due to my setup),
so text I try to type into Outlook ends up in
*scratch*. That's creepy weird.
I'm not familiar with that variable, and I don't
really make much, if any, real use of Eldoc, but
if other users also find Eldoc periodically stealing
focus from other window-mgr windows and redirecting
it to some Emacs frame I'd think that would be quite
annoying. (Has anyone reported that?)
Good thing I have it set to nil, I guess.
next prev parent reply other threads:[~2019-01-19 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 9:32 eldoc vs minibuffer-auto-raise martin rudalics
2019-01-19 16:20 ` Drew Adams
2019-01-19 18:49 ` martin rudalics
2019-01-19 19:24 ` Eli Zaretskii
2019-01-20 9:13 ` martin rudalics
2019-01-19 22:25 ` Drew Adams [this message]
2019-01-20 9:18 ` 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=751af5b0-cfe6-4887-8489-0f40b0be0d75@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).