From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: RE: Do not switch focus to the completions buffer window
Date: Thu, 6 Feb 2014 19:44:49 -0800 (PST) [thread overview]
Message-ID: <af32981b-899c-43e1-9156-7b5366722848@default> (raw)
In-Reply-To: <87r47fpqkb.fsf@web.de>
> The *Completions* window is never selected for me. I tested with
> Emacs 23 and Emacs 24. Even better, with the latest Emacs release,
> the *Completions* pop up window is even automatically closed after
> successful completion.
>
> So I think what you see is caused by your setup, or you use a really
> old Emacs version. Or please give a recipe of what you see starting
> from emacs -Q.
Perhaps Leo is doing something like this?
emacs -Q
(setq pop-up-frames t)
M-x for TAB
That's enough, on MS Windows at least, to repro the problem.
When MS Windows creates a new frame, it gives it the input
focus. Anything you type after the TAB above will be sent
to *Completions*.
This has been a limitation of Emacs since forever, and a
limitation that I, for one, jump through some hoops to
workaround. (And it was a problem solved by the Epoch
version of Emacs 20 years ago.)
Dunno whether this is in fact related to Leo's actual problem.
But it is one possible scenario that leads to the problem
Leo described.
prev parent reply other threads:[~2014-02-07 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:24 Do not switch focus to the completions buffer window Leo Alekseyev
2014-02-07 3:08 ` Michael Heerdegen
2014-02-07 3:44 ` Drew Adams [this message]
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=af32981b-899c-43e1-9156-7b5366722848@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).