From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: completing-read (and M-x) with pop-up-frames non-nilchangesframefocus
Date: Wed, 20 Jul 2005 18:09:09 -0400 [thread overview]
Message-ID: <E1DvMkX-0000Xa-5J@fencepost.gnu.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICIEMFCKAA.drew.adams@oracle.com>
My bad. So users must set it, to tell Emacs about the window manager. But
couldn't the default value be defined reasonably for a few common window
managers?
In most window managers, this behavior is customizable. And I don't
know if there is even a way to find out which window manager is
running, on most systems. I don't know if there is a way to find out
what the setting is.
Maybe some X expert could find out to what extent Emacs could
find this out.
But what about Stefan's patch? It sounded like it might take care of this
annoyance.
I don't recall what that patch was.
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.
next prev parent reply other threads:[~2005-07-20 22:09 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 [this message]
2005-07-20 22:51 ` Henrik Enberg
2005-07-20 22:57 ` Jan D.
2005-07-20 23:19 ` completing-read (and M-x) with pop-up-framesnon-nilchangesframefocus Drew Adams
2005-07-21 17:08 ` 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
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=E1DvMkX-0000Xa-5J@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/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).