Hi Gregor,
> The most usable approach would indeed be to set the terminal name (for
> example to mocp_float) and to add a floatapps entry for it. On the other
> hand, if you don't want to clutter your floatapps, you could set some
> global variable to true before spawning the xterm. Then check in your
> manage hook if that variable is true and if so, set the managed client
> floating and the variable to false (i.e. something like
> float_next_client or something). The first approach is much more sane
> and error-proof though.
Mmmh... I give it a try... Another boring question, are floatapps' name
"string value matched" or through "pattern matching":
floatapps = {
...
["__FLOAT__"] = true,
...
}
If i spawn a "xterm -e mocp -n test__FLOAT__", will it be matching the
floatapps' rule (since it contains "__FLOAT__") or i have to spawn as
"xterm -e mocp -n __FLOAT__"?
Thanks a lot.
ff0000
--
To unsubscribe, send mail to [email protected].
