unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: raise frame no go
Date: Mon, 24 Sep 2007 07:53:10 +0200	[thread overview]
Message-ID: <46F750C6.7080704@swipnet.se> (raw)
In-Reply-To: <m2vea1r4ve.fsf@cam.ac.uk>



Leo skrev:
> On 2007-01-06 12:32 +0000, Jan Djärv wrote:
>> Eli Zaretskii skrev:
>>>> Date: Thu, 04 Jan 2007 12:42:19 +0100
>>>> From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= <jan.h.d@swipnet.se>
>>>> Cc: emacs-pretest-bug@gnu.org
>>>> Metacity (the default Gnome window manager)  is a complete mess when it comes 
>>>> to raise frame.  Some versions works, some don't.  Some require the code 
>>>> below, some don't.  In some configurations (i.e. focus on click vs. focus on 
>>>> mouse) raise frame works, in some raise frame don't work.
>>>>
>>>> We must give up on creating workarounds for Metacity, and just tell people 
>>>> that metacity is buggy.  Ufortunately they have to figure out a workaround for 
>>>> themselves and their specific verion/configuration of metacity.
>>> How about writing an entry for etc/PROBLEMS about this?
>> In the bug created by Leo, http://bugzilla.gnome.org/show_bug.cgi?id=392889,
>> the recommendation from the Gnome people seems to be that we use
>> _NET_ACTIVE_WINDOW but with a proper timestamp (this was wrong in Emacs).  If
>> some version of Metacity hangs, it is no fault of Emacs and should be handeled
>> as a Metacity bug.
>>
>> On the other hand, it is late in the game (pretest-wise) and maybe a note in
>> etc/PROBLEMS is good enough for the release.
>>
>> Comments?
>>
>> 	Jan D.
> 
> Has this been fixed?
> 

raise-frame does not do _NET_ACTIVE_WINDOW, but x-focus-frame does.  It would 
be trivial to add, but the latest discussion indicated that people didn't want 
that.  I.e. raise-frame should just do that, raise.  Focus should stay where 
it was.  But for metacity, there is no way to do that.

	Jan D.

  reply	other threads:[~2007-09-24  5:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2ac0z5q7a.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found] ` <459CE81B.2090201@swipnet.se>
     [not found]   ` <uhcv61o2b.fsf@gnu.org>
2007-01-06 12:32     ` raise frame no go Jan Djärv
2007-01-07  3:47       ` Richard Stallman
2007-01-08  7:43         ` Jan Djärv
2007-01-07 15:45       ` Stefan Monnier
2007-01-07 16:58         ` Mathias Dahl
2007-01-13 19:04           ` Mathias Dahl
2007-01-08  7:45         ` Jan Djärv
2007-01-08 15:19           ` Stefan Monnier
2007-01-08 17:40             ` Jan Djärv
2007-01-08 23:34               ` Stefan Monnier
2007-01-09  7:18                 ` Jan Djärv
2007-01-10 21:47                   ` Miles Bader
2007-01-11  0:28                     ` Chris Moore
2007-01-11  7:48                     ` Jan Djärv
2007-09-23 11:35       ` Leo
2007-09-24  5:53         ` Jan Djärv [this message]
2007-09-24  8:40           ` Leo

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=46F750C6.7080704@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.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).