Re: rename-window far from beeing perfect


Isn't it ok to have rename-window as a practical hack against ICCCM?
It's the fact that there're crazy titles set by clients. But at least,
it should be documented that it's a mere resort.

It is also possible to put it on Scripts page in wiki, rather than
adopting in the trunk. I'm not sure which is right. Anyway, thank you
Timo for notice.

On Mon, 14 Sep 2009 18:56:20 +0300, Timo Korvola wrote:
> The entire rename-window feature is something like a bug.  It is  
> forbidden in the ICCCM for the wm to change WM_NAME and other such 
> properties written by the client (see 4.1.2 Client Properties, first 
> paragraph).  _NET_WM_NAME is part of EWMH and not in the ICCCM, but 
> because _NET_WM_NAME is intended as a UTF-8 replacement for WM_NAME, it 
> would seem reasonable to expect the same behaviour.

On Mon, 14 Sep 2009 15:42:00 +0200, Christopher Roy Bratusek wrote:
> [On] rename-window [...]  when an app changes the (_NET_)WM_NAME on it's
> own, our customized one is beeing erased

Is it possible to react with property-notify-hook or things like that?
In that case, I think this kind of code should go into user contrib
scripts, not into trunk.

Teika (Teika kazura)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]