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, t
I'm far from sure it'll fix the bug and if it doesn't, I'd rather not
install it, so please have someone try it before I install it,
I agree, but I don't have a way to check it myself.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http
> 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.
I'm far from sure it'll fix the bug and if it doesn't, I'd rather not
install it, so please have someone try
> 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 o
> 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,
Stefan
--- window.c13 jui 2005 13:58:39 -0400 1.512
+++ window.c15 jui 2005 03:30:07 -0400
@@ -3475,7 +347
> 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 st
