Hi,

+1 to the window selector. I have spent some time looking into this right
now, and the answer is something like this:
win=`wmctrl -l |  cut -d ' ' -f5- | dmenu -i` && wmctrl -a $win

Put that in a shell script and bind it to some key (make sure you have
installed 'wmctrl' before), and you will be able to change the window :)

Also, I agree with you with the renaming tags issue.

Cheers everyone, and congratulations on releasing version 3.4.

On Tue, Oct 20, 2009 at 10:29 PM, Emmanuel Oga <[email protected]>wrote:

> Hello guys,
>
> I've been using awesome for a while now (couple of months). It is
> working nicely for me but I find a couple of problems I'm not sure how
> to deal with.
>
> This is how I've been using awesome so far:
>
> I start up a couple of apps for each tags. I have the std awesome 1-9
> tags. So, for example, I have a couple of vims on tag 1, a couple of
> consoles on tag 2, and so on.
> Usually, I modkey+space each layout until I get it how I like, then
> adjust the ratios of the layout until I reach happiness.
>
> Problems:
>
> * Whenever I need to find a specific window, I need to modkey-1.to.9
> to find it. I know there is a window list if I click with the mouse,
> but using he mouse is suboptimal. Ideally I would like to have
> something like vim's fuzzyfilefinder but for awesome client
> names/classes.
> * I can't find an easy way of renaming tags. Is it at all possible
> without using something like Shifty? (The reason I don't want to use
> Shifty *yet* is there has to be an easier way of doing that with plain
> old AWM, right?)
> * Is there any way of persisting the layout/cleints without having to
> script that "manually" ? Example, in wmii you can persist your layout,
> so if you want to have one screen with say,. one vim at the right, one
> firefox to the left, you can do it using the command line.
>
> BTW; yes, I read the man page and browsed the wiki, if you think I
> missed something please, could you provide a link to the info about
> it? Thanks in advance!
> and BTW #2: I'm ok if the solution is "you want it, code it yourself,
> that's why the conf is  written in lua". But, if at all possible, I
> would like to avoid wheel reinventions.
> --
> --------------------------------------------------------------
> EmmanuelOga.com - Software Developer
>
> --
> To unsubscribe, send mail to [email protected].
>

Reply via email to