From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: completing-read (and M-x) with pop-up-framesnon-nilchangesframefocus
Date: Wed, 20 Jul 2005 16:19:56 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICCEMJCKAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1DvMkX-0000Xa-5J@fencepost.gnu.org>
But what about Stefan's patch? It sounded like it might
take care of this annoyance.
I don't recall what that patch was.
See below.
The problem arises because one frame's minibuffer is
expecting input, while
another frame (*Completions*) gets created and selected
(depending on the
window manager). The input dialog gets totally lost (interrupted),
systematically.
Why doesn't Emacs move the minibuffer onto the frame that is selected?
I thought there was code to do that.
That would be great. But how would that affect a standalone minibuffer (in a
separate frame)? I use that, and I use a dedicated frame for *Completions*
and explicitly redirect its focus to the minibuffer frame. Could something
like that perhaps be done by default when default-frame-alist has minibuffer
property = nil?
Stefan's patch (untested on Windows):
-----Original Message-----
From: Stefan Monnier [mailto:monnier@iro.umontreal.ca]
Sent: Friday, July 15, 2005 12:36 AM
To: Drew Adams
Cc: Emacs-Devel
Subject: Re: completing-read (and M-x) with pop-up-frames non-nil
changes frame focus
> 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.c 13 jui 2005 13:58:39 -0400 1.512
+++ window.c 15 jui 2005 03:30:07 -0400
@@ -3475,7 +3475,13 @@
we need to create a new frame. */
if (pop_up_frames || last_nonminibuf_frame == 0)
{
+ Lisp_Object w = Fselected_window ();
+ struct gcpro gcpro1;
+ GCPRO1 (w);
window = Fframe_selected_window (call0 (Vpop_up_frame_function));
+ if (Fwindow_live_p (w))
+ Fselect_window (w, Qt);
+ UNGCPRO;
Fset_window_buffer (window, buffer, Qnil);
return display_buffer_1 (window);
}
next prev parent reply other threads:[~2005-07-20 23:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 3:35 completing-read (and M-x) with pop-up-frames non-nil changes frame focus Drew Adams
2005-07-15 5:27 ` Stefan Monnier
2005-07-15 7:35 ` Stefan Monnier
2005-07-15 14:07 ` Drew Adams
2005-07-15 20:45 ` Stefan Monnier
2005-07-15 20:55 ` Drew Adams
2005-07-18 4:48 ` Richard M. Stallman
2005-07-18 5:10 ` completing-read (and M-x) with pop-up-frames non-nil changes framefocus Drew Adams
2005-07-18 21:23 ` Richard M. Stallman
2005-07-18 22:14 ` completing-read (and M-x) with pop-up-frames non-nil changesframefocus Drew Adams
2005-07-19 20:32 ` Richard M. Stallman
2005-07-19 21:04 ` completing-read (and M-x) with pop-up-frames non-nilchangesframefocus Drew Adams
2005-07-20 22:09 ` Richard M. Stallman
2005-07-20 22:51 ` Henrik Enberg
2005-07-20 22:57 ` Jan D.
2005-07-20 23:19 ` Drew Adams [this message]
2005-07-21 17:08 ` completing-read (and M-x) with pop-up-framesnon-nilchangesframefocus Richard M. Stallman
2005-07-21 18:25 ` Stefan Monnier
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=DNEMKBNJBGPAOPIJOOICCEMJCKAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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.