Re: Possibility to send app to certain tag on 'active' screen?

2011/7/6 Michał Janke : >>> >>> So awful.rules doesn't provide what you want. >>> But don't worry, you can have a callback! >>> >>> callback = function(c) >>>   c.screen = mouse.screen >>>   c:tags({ tags[c.screen][3

Re: Possibility to send app to certain tag on 'active' screen?

>> >> So awful.rules doesn't provide what you want. >> But don't worry, you can have a callback! >> >> callback = function(c) >>   c.screen = mouse.screen >>   c:tags({ tags[c.screen][3] }) >> end >> > > Man, this is really crazy. I have the same problem: > Create a rule that makes new windows appe

Re: Possibility to send app to certain tag on 'active' screen?

2011/4/12 Uli Schlachter : > Am 12.04.2011 06:04, Adrian C. wrote: >> >> On Tue, 12 Apr 2011, Oon-Ee Ng wrote: >> >>> The answer I was given is that mouse.screen is fixed from the time >>> awesome is started >> >> You are doing an assignment to 'tag', rules are interpreted and the >> value is store

building awesome-3.4.9 fails at manpages

Hi, everyone. I'm having problems with 3.4.9 failing to build. Here's what I get: (...) [ 41%] Generating themes/default/titlebar/sticky_normal_inactive.png [ 41%] Generating themes/default/titlebar/maximized_normal_inactive.png [ 61%] Built target generated_icons [ 61%] Built target luadoc [ 61%

Re: Blurry alpha elements + flickering

2010/3/18 Julien Danjou : > > I replied to Michał directly by mistake. Problem is its background > setter tool, obviously. > > Michał Janke writes: > >> Wow! You really hit the spot at first shot (was it that obvious?). Why >> didn't I check that earlier..