unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chip Coldwell <coldwell@redhat.com>
Cc: emacs-devel@gnu.org
Subject: Re: raise-frame doesn't work in Fedora Core 4
Date: Thu, 2 Nov 2006 12:46:24 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0611021127240.2445@localhost.localdomain> (raw)
In-Reply-To: <E1GerXw-00068h-00@etlken>

On Tue, 31 Oct 2006, Kenichi Handa wrote:
>
>>>>>> In the emacs-pretest-bug list, Katsumi Yamaoka wrote:
>
>> I did them in the Fedora Core 4 platform.  Since `raise-frame'
>> does nothing in this platform, I'm trying to advise it to be
>> replaced with `delete-frame' and `make-frame' as follows:
>
> That `raise-frame' didn't work was a life-and-death problem for
> me.  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 haven't been able to locate a bug for this in bugzilla.redhat.com.
I'm coming late to this thread -- did you try the emacs-22.0.90
pretest?  M-x raise-frame works for me on Fedora Core 5 with this
version.  I've built some test rpms for FC-5 and FC-6 and put them
here:

http://people.redhat.com/coldwell/bugs/emacs/176171/

Chip

-- 
Charles M. "Chip" Coldwell
Senior Software Engineer
Red Hat, Inc
978-392-2426

  parent reply	other threads:[~2006-11-02 17:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 11:12 raise-frame doesn't work in Fedora Core 4 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 [this message]
2006-11-02 19:25   ` Chip Coldwell
     [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
2007-09-16 10:25     ` Jan Djärv

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=Pine.LNX.4.64.0611021127240.2445@localhost.localdomain \
    --to=coldwell@redhat.com \
    --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).