From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: raise-frame doesn't work in Fedora Core 4
Date: Wed, 01 Nov 2006 08:24:59 +0100 [thread overview]
Message-ID: <45484BCB.8060902@swipnet.se> (raw)
In-Reply-To: <E1Gf5cp-0001L8-3m@fencepost.gnu.org>
Richard Stallman skrev:
> Now I realized I can use the program called `wmctrl'[1] to solve
> the problem. Here's an new advice:
>
> (defadvice raise-frame (after make-it-work (&optional frame) activate)
> "Make it work."
> (call-process
> "wmctrl" nil nil nil "-i" "-R"
> (frame-parameter (or frame (selected-frame)) 'outer-window-id)))
>
> That is an ugly solution. How does the wmctrl program actually do
> this?
It figures out the current desktop (i.e. if you have more than one
workspace/desktop) by inspecting the property _NET_WM_DESKTOP or
_WIN_WORKSPACE on the root window. It then switches the window to the current
desktop by sending a client message _NET_CURRENT_DESKTOP. Finally it
activates the window by sending the client message _NET_ACTIVE_WINDOW.
So it does more than the patch sent erlier in this thread.
>
> I have only the knowledge that Fedora Core 4
> uses the metacity window manager, sorry.
>
> Does this use of wmctrl work correctly with other window managers?
It works with window managers that understand and comply with the newest
freedesktop Window Manager Specification
(http://freedesktop.org/wiki/Standards_2fwm_2dspec), i.e. Metacity (Gnome),
KWin (KDE), xfwm4 (xfce) and other newer window managers. There is a list on
the web page. Certainly not with older VM:s like twm and mwm.
Jan D.
next prev parent reply other threads:[~2006-11-01 7:24 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 [this message]
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
[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=45484BCB.8060902@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).