Re: Awesome 3.5 split different behaviour than in 3.4.15

2013-07-31 Thread Wojciech Daniło
That's strange because my awesome 3.14 config always when opening new window keeped the one on the left and added new windows to the right stack - anyway is it possible somehow to change the bahavior to the one I'm describing here? 2013/7/31 jk121...@gmail.com Actually the behavior you

Re: Awesome 3.5 split different behaviour than in 3.4.15

2013-07-31 Thread Marco
On 2013–07–31 Wojciech Daniło wrote: That's strange because my awesome 3.14 config always when opening new window keeped the one on the left and added new windows to the right stack - anyway I can confirm Gerald's findings, it's the same here. 1) Which layout do you use? 2) Did you try with

Opening Apps On Screens

2013-07-31 Thread Gerald Klein
Hi, I have a little problem, I load MPlayer into screen 2 tag 1, now when I start VMWare (vmplayer) it loads into screen 2 tag 1, Not earth shattering problem but kind of annoying because I load multiple vm's at once and they all head for that tag. I tested it by changing the rule to put MPlayer

Re: Opening Apps On Screens

2013-07-31 Thread Ignas Anikevičius
Hi, On Wednesday 31 July 2013 04:52:59 Gerald Klein wrote: The classes for the windows are similar but not the same and it seems like the matching is using a contains and not an equals, is there a way to make this work right? Vmplayer and vmplayer MPlayer and mplayer Could you post your

Re: Opening Apps On Screens

2013-07-31 Thread jk121960
HI and thanks, I don’t use that part of the command structure but here are my rules awful.rules.rules = { -- All clients will match this rule. { rule = { }, -- properties = { border_width = beautiful.border_width, -- border_color = beautiful.border_normal, --