From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, handa@m17n.org
Subject: Re: raise-frame doesn't work in Fedora Core 4
Date: Thu, 02 Nov 2006 09:23:47 +0100 [thread overview]
Message-ID: <85u01i5ka4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <45499E95.1080403@swipnet.se> (Jan Djärv's message of "Thu\, 02 Nov 2006 08\:30\:29 +0100")
Jan Djärv <jan.h.d@swipnet.se> writes:
> Richard Stallman skrev:
>
> I think sending the _NET_ACTIVE_WINDOW is correct here according to
> the new specification.
>
>> Is it right to move the window to the current desktop?
>
> It depends on how we want raise-frame to behave. Do we want Emacs
> to switch the frame to the current desktop or not? To not switch is
> the current implementation so if we want to change I suggest next
> release.
If the frame was iconified previously, switching it to the current
desktop would warrant a user-configurable option, I think (defaulting
to "off"). If it was _not_ iconified previously, I think it would be
very wrong to change the overall window configuration by moving frame
around.
>> What happens if you do this (via wmctrl or directly) and you're
>> using an older wm? Does it do any harm?
>
> No, it becomes a noop. The client message gets sent to the root
> window but since nobody (i.e. the window manager) isn't listening
> for it, nothing more happens.
Sounds like something we should likely do then.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-11-02 8:23 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 [this message]
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=85u01i5ka4.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=rms@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).