[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: completing-read (and M-x) with pop-up-frames non-nil changes frame f

From: Drew Adams
Subject: RE: completing-read (and M-x) with pop-up-frames non-nil changes frame focus
Date: Fri, 15 Jul 2005 07:07:51 -0700

    > emacs -q
    > M-x set-variable pop-up-frames t
    > M-x complet TAB

    > This opens a new frame for buffer *Completions*. At least in
    Windows, the
    > new frame is selected. The frame focus for typing key sequences thus
    > switches to the *Completions* frame, but the minibuffer of
    the original
    > frame is still waiting for input. So, you cannot continue to type, to
    > disambiguate the command you want.

    Maybe this is related to the following comment in the docstring of

       This function itself does not make the new frame the selected frame.
       The previously selected frame remains selected.  However, the
       window system may select the new frame for its own reasons, for
       instance if the frame appears under the mouse pointer and your
       setup is for focus to follow the pointer.

    So maybe Fdisplay_buffer should protect against it with
    something like the
    patch below.  Does it help?

  Sorry about the botched patch.  Try this one instead,

Thanks for considering this a bug - I wasn't sure it would be looked at that

I can't build from C sources and test this myself, but I'll take your word
for it that it's fixed. If someone else happens to do a Windows build,
perhaps s?he could confirm.  Thanks.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]