From: Katsumi Yamaoka <yamaoka@jpl.org>
To: emacs-devel@gnu.org
Subject: Re: raise-frame doesn't work in Fedora Core 4
Date: Fri, 14 Sep 2007 15:24:57 +0900 [thread overview]
Message-ID: <b4mps0l3gsm.fsf@jpl.org> (raw)
In-Reply-To: b9yzmtbv040.fsf_-_@jpl.org
Hi again,
I recalled this bug has not been solved yet.
>>>>> Katsumi Yamaoka wrote:
> For instance, I couldn't make the Emacs frame (which was
> existing but was lowered behind the other frames) pop to the
> front using `C-x 5 b'.
I'm now in Fedora 7 that I update everyday. It runs the metacity
window manager and the problem seems to happen only with LUCID
(not GTK) Emacs on it. The concrete way to reproduce this bug is:
1. Start Emacs with the -Q option.
2. Type `C-x 5 b *Messages* RET'.
Now there are two Emacs frames as follows:
+-------------+
| |
| +--------------+
| | |
| *sc| |
+-----| |
| *Messages* |
+--------------+
3. Select the *scratch* frame by the mouse.
+-------------+
| |
| |------+
| | |
| *scratch* | |
+-------------+ |
| *Messages* |
+--------------+
4. Type `C-x 5 b *Messages* RET' in the *scratch* frame.
But the *Messages* frame is neither raised nor focused.
Jan Djärv wrote to me a half year ago in:
http://www.mail-archive.com/emacs-pretest-bug@gnu.org/msg11474.html
> See http://bugzilla.gnome.org/show_bug.cgi?id=392889. My last comment
> was that we may enable _NET_ACTIVATE_WINDOW, but it has been postponed
> to after the release.
The problem I brought up then seems to have been solved now.
However, it seems to be likely different from this. The whole
thread that contain this article is:
http://news.gmane.org/group/gmane.emacs.devel/thread=61471/force_load=t
Regards,
next prev parent reply other threads:[~2007-09-14 6:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b9yoe9xece4.fsf@jpl.org>
2005-06-27 23:41 ` raise-frame doesn't work in Fedora Core 4 (was Re: `make-frame' makes...) Katsumi Yamaoka
2005-06-28 15:48 ` raise-frame doesn't work in Fedora Core 4 Johan Bockgård
2007-09-14 6:24 ` Katsumi Yamaoka [this message]
2007-09-16 10:25 ` Jan Djärv
2006-10-31 11:12 Kenichi Handa
2006-10-31 11:57 ` Katsumi Yamaoka
2006-10-31 12:24 ` Jan Djärv
2006-10-31 15:37 ` Stefan Monnier
2006-10-31 17:19 ` Jan D.
2006-10-31 19:01 ` Stefan Monnier
2006-11-01 7:08 ` Jan Djärv
2006-11-01 23:15 ` Chong Yidong
2006-11-01 23:21 ` David Kastrup
2006-11-02 16:48 ` Stefan Monnier
2006-11-02 21:47 ` Richard Stallman
2006-11-01 3:50 ` Masatake YAMATO
2006-11-01 4:51 ` Katsumi Yamaoka
2006-11-01 2:14 ` Richard Stallman
2006-11-01 7:28 ` Jan Djärv
2006-11-01 16:43 ` Stefan Monnier
2006-11-02 4:43 ` Richard Stallman
2006-11-02 7:56 ` Jan Djärv
2006-11-02 16:45 ` Stefan Monnier
2006-11-03 7:54 ` Jan D.
2006-11-03 8:55 ` Jan D.
2006-11-03 8:59 ` Jan D.
2006-11-09 10:27 ` Katsumi Yamaoka
2006-11-01 2:14 ` Richard Stallman
2006-11-01 7:24 ` Jan Djärv
2006-11-02 4:42 ` Richard Stallman
2006-11-02 7:30 ` Jan Djärv
2006-11-02 8:23 ` David Kastrup
2006-11-03 7:07 ` Richard Stallman
2006-11-02 17:46 ` Chip Coldwell
2006-11-02 19:25 ` Chip Coldwell
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=b4mps0l3gsm.fsf@jpl.org \
--to=yamaoka@jpl.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 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.