patch for tabbing extension correcting the x window properties
schmorp at schmorp.de
Tue Mar 9 16:03:45 CET 2010
On Tue, Mar 09, 2010 at 02:49:46PM +0100, Brian 'morlenxus' Miculcy <morlenxus at gmx.net> wrote:
> So this is a problem which exists and which isn't a problem of the window manager, simply other window manager don't allow to restart itself, in short, this is a bug. I guess IceWM does read the window properties more often instead of caching and that's why it's also happen there.
Of course it's a problem with the window manager: the behaviour makes no
sense, other window managers don't do it.
You might not call it a bug in the wm, but it is extremely stupid
> Again, it is NOT a bug in the window manager, it is a bug in the tabbing code.
It's of course not a bug in the tabbing code, as I explained
before! Please don't repeat bullshit claims - that is not constructive and
doesn't result in a helpful atmosphere.
> The solution itself is simple: Just don't give the main window the _XEMBED_INFO and everything is ok. :)
Or fix enlightenment to not ignore toplevel windows it clearly should
xembed properties are valid on toplevel windows, and if enlightenment gets
digestion errors because of them, that's purely enlightenments problem.
Higher quality window managers do the right thing. Window managers do not
*have* to manage all windows, but if they don't and it is a problem, it's
a problem in the wm.
> Hopefully it's now clear how the problem appears and how to fix it.
The problem exists in enlightenment, and no way of tinkering in urxvt can
fix it, as it will happen with other applications as well.
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp at schmorp.de
More information about the rxvt-unicode