[TAG] : Window Manager in FC5
francis at daoine.org
Thu Jan 4 00:56:00 MSK 2007
On Wed, Jan 03, 2007 at 07:05:11AM +0000, Thomas Adam wrote:
> On Tue, Jan 02, 2007 at 11:15:40PM +0000, Francis Daly wrote:
> > which allows me play with a window manager in a sort-of-sandbox. Be
> > aware of the order in which programs see keypresses, though, because
> > nesting within a "greedy" window manager might cause a head-scratch.
> That's not the problem; the problem is the fact that Xnest emulates both
> an XServer and an XClient, and its implementation as to how key-bindings
> are interpreted/propagated within itself and to the underlying XCient
> (Xnest in this case) don't always tally -- the confusion lies solely
> with Xnest in this regard.
That's certainly *a* problem, but wasn't what I was thinking of.
I was more considering where the main window manager handles some
keypresses itself, and where some client of the nested X server,
including the window manager, wants to be able to receive those same
Hopefully the window managers have a mechanism of sending any keypress
through to an app; my point was that in order to send a keypress through
to, for example, a client of the nested X server, you would need to take
account of the mechanisms of both window managers rather than just the
nested one. So it's not a "clean" window manager environment.
And that's because the main window manager gets to handle the keypress
before the nested X server (which then plays its own games before the
nested window manager sees anything).
I lied. I don't use Xnest to play with a window manager. I use it to play
with other applications under a window manager other than the one I
And yes, running under Xnest does add some extra wrinkles. "sometimes
sticky control key" is one that catches me, but that could just be a
feature of how I use it.
Francis Daly francis at daoine.org
More information about the TAG