Matthias Kirschner wrote:
Hi Ben,
* Ben Hodgens <[email protected]> [2009-05-31 14:40:40 -0600]:
The only thing I wish it had was a "GUI" way to associate clients with a
tag (for automatic assignment) and to remember the specific predefined
view per tag. It's a little irritating to have to configure, but it works
just the same once you figure it out. :)
I am using awesome for about a week now. The clients / tag associaten
works fine. But I haven't had time to look into the "remember predifined
view per tag" yet. Can you give me a pointer, or the corresponding part
of your config?
Thanks,
Matthias
Which version of Awesome are you using, Matthias? Version 3.2 and 3.3 have
drastically different configurations (3.3 is all-lua, 3.2 still has some of the
legacy configuration left). I can't rightly say what 3.3 would look like, but
here's what 3.2 looks like (3.3 should be similar; I think this part of the
config is in lua):
-- Applications to be moved to a pre-defined tag by class or instance.
-- Use the screen and tags indices.
apptags =
{
-- ["Firefox"] = { screen = 1, tag = 2 },
-- ["mocp"] = { screen = 2, tag = 4 },
}
The "class or instance" part is kinda time consuming, and why I've not gotten
around to doing it yet (also due to simply suspending/hibernating instead of
shutting down). It's queried from the clients via the xprop and xwininfo tools.
Something like this would be useful for finding this info:
#!/bin/bash
sleep 5
WIN_ID=`xprop -root | grep "_NET_ACTIVE_WINDOW(WINDOW)"| cut -d ' ' -f 5`
xwininfo -id $WIN_ID |awk 'BEGIN {FS="\""}/xwininfo: Window id/{print $2}' | sed
's/-[^-]*$//g'
Throw that in a bash script, switch to the client in question, and you sh
Apparently some applications do not report the window name properly, thus why
it's "class or instance" (as I understand it). Someone please correct me if I'm
wrong.
--
Benjamin Hodgens
[email protected]
Home: 605-343-8835
Cell: 605-430-0601
--
To unsubscribe, send mail to [email protected].
