From: Chong Yidong <cyd@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12139@debbugs.gnu.org
Subject: bug#12139: 24.1; `occur-edit-mode' is completely broken if `pop-up-frames'=t
Date: Mon, 06 Aug 2012 12:18:37 +0800 [thread overview]
Message-ID: <87d334r6ua.fsf@gnu.org> (raw)
In-Reply-To: <48173DDBBBAE44A5A1C554D35BC9122D@us.oracle.com> (Drew Adams's message of "Sat, 4 Aug 2012 13:52:38 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> emacs -Q
> (setq pop-up-frames t)
> In some buffer, M-x occur, then `e' to enter `occur-edit-mode'.
>
> Type a character on the occur buffer. The frame of the buffer that was
> searched is brought to the foreground, obscuring the occur buffer.
> What's more, the searched buffer's frame receives the input focus.
It's a long-standing issue with display-buffer. The docstring of
display-buffer says
Display BUFFER-OR-NAME in some window, without selecting it.
But when pop-up-frames is non-nil, display-buffer does explicitly select
the window, via raising its frame. One could argue that this is
desirable because the frame that is being re-used might be obscured or
out of sight, but it interferes with Lisp callers which want to display
stuff in another window without losing focus from the current one (which
is the main role of display-buffer).
next prev parent reply other threads:[~2012-08-06 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 20:52 bug#12139: 24.1; `occur-edit-mode' is completely broken if `pop-up-frames'=t Drew Adams
2012-08-06 4:18 ` Chong Yidong [this message]
2012-08-06 5:28 ` Chong Yidong
2012-08-06 6:17 ` Drew Adams
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=87d334r6ua.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=12139@debbugs.gnu.org \
--cc=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 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).