all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: 12139@debbugs.gnu.org
Subject: bug#12139: 24.1; `occur-edit-mode' is completely broken if `pop-up-frames'=t
Date: Sat, 4 Aug 2012 13:52:38 -0700	[thread overview]
Message-ID: <48173DDBBBAE44A5A1C554D35BC9122D@us.oracle.com> (raw)

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.
 
In sum, you cannot edit the occur buffer at all, because all input takes
place in the searched buffer, and its frame is popped up, in front, each
time you make any change in the occur buffer.
 
This bug is a POSTER CHILD for Emacs Dev's introducing a feature without
ever testing it with a non-nil `pop-up-frames' scenario (or the
equivalent).

In GNU Emacs 24.1.1 (i386-mingw-nt5.1.2600)
 of 2012-06-10 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include'
 






             reply	other threads:[~2012-08-04 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 20:52 Drew Adams [this message]
2012-08-06  4:18 ` bug#12139: 24.1; `occur-edit-mode' is completely broken if `pop-up-frames'=t Chong Yidong
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48173DDBBBAE44A5A1C554D35BC9122D@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12139@debbugs.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 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.