From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: override_redirect of X Window System
Date: Wed, 24 Sep 2003 20:17:47 +0200 [thread overview]
Message-ID: <669F8BA2-EEBB-11D7-8175-00039363E640@swipnet.se> (raw)
In-Reply-To: <1064425246.8452.1.camel@littlegreen>
> On Wed, 2003-09-24 at 18:14, Jan D. wrote:
>>> It is not a metacity bug - there is an agreed upon protocol for full
>>> screening windows, and override-redirect is not it.
>>
>> http://bugzilla.gnome.org/show_bug.cgi?id=106740
>
> This is about being able to move windows above panels for accessibility
> reasons, not how apps are supposed to fullscreen.
And that is what I said.
>
>>> To Kazu: I'd recommend you research the latest EWMH specification,
>>> that
>>> will show you how to properly fullscreen windows.
>>
>> This requires XSendEvent. It is not available from elisp.
>> It is also not a solution that works on all window managers out there.
>
> It works on all standards compliant WMs, which is an increasing number.
> There's no need to expose XSendEvent to elisp, simply having a
> fullscreen function that does the necessary machinery would work too.
The good things about standards is that there are so many to choose
from :-)
Seriously, there are WMs that where created before EWMH existed. One
is CDE, which is used a lot. Others in use still, are fvwm 1.x, olvwm,
mwm and KDE 1.x.
If we add a solution to Emacs that says "call this function to get
fullscreen" and then it does not work on peoples WMs, I think we are
going to see bug reports. And if there is one response I don't like
w.r.t. things that doesn't work, it is "please change your
unrelated app/version/OS... to something else".
Exposing XSendEvent can be potentially useful for more things than
fullscreen. For example, expand vertically and/or horizontally that
are also in EWMH.
But I do not make these desicions for Emacs, these are just my opinions.
If it is descided to put in a C-function that only works on a subset of
X window WMs, I can implement it. But I think my suggestion is more
portable and more useful (hardly surprising :-)
Jan D.
next prev parent reply other threads:[~2003-09-24 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 2:45 override_redirect of X Window System Kazu Yamamoto
2003-09-18 11:05 ` Richard Stallman
2003-09-19 15:24 ` Jan D.
2003-09-22 17:32 ` Mike Hearn
2003-09-24 17:14 ` Jan D.
2003-09-24 17:40 ` Mike Hearn
2003-09-24 18:17 ` Jan D. [this message]
2003-09-25 9:56 ` Mike Hearn
2003-09-25 21:08 ` Jan D.
2003-09-25 22:06 ` Kim F. Storm
2003-10-05 17:11 ` Jan D.
2003-10-08 0:04 ` Kazu Yamamoto
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=669F8BA2-EEBB-11D7-8175-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
--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).