Hi Ben,
* Ben Hodgens <[email protected]> [2009-05-31 17:38:49 -0600]:
> 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):
Sorry about that. I use awesome since a week and currently it is
"awesome v3.3-rc4".
> -- 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 },
> }
Yes, that was very good documented in rc.lua.
> 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.
Hm, either I don't understand the bash script above or I misunderstood
you in the first place. I thought you have a solution to define that
when I start awesome on tag 1 the view mode is "max", on tag 2 it is
"fairv", on tag 3 it is "fairh", ...
Best wishes,
Matthias
--
Why join FSFE's Fellowship? (http://fellowship.fsfe.org)
--
To unsubscribe, send mail to [email protected].
