Am 03.04.2014 07:50, schrieb Uli Schlachter: > You aren't spawning a client and throwing it away. You are spawning a > *process*. That process later happens to open a new window and thus we > get a client, but not all processes open one window. Ah, that's definitely true, obviously slipped my mind yesterday.
> [awesome awesome-code] > Why is this better than just finding the new urxvt by pid in the manage > hook? Dunno. It just gets more browny points for using some fancy API... I assume this set xproperty persists as long as the X-Server is up and running (aka over restarts of awesome)? That would solve another issue, tracking this urxvt over restarts of awesome (shall be spawned once, but not again when I restart awesome as it still fullfills its purpose). If so, the xproperty-String can be chosen as I see it fit, right? Thanks, Manuel -- To unsubscribe, send mail to [email protected].
