Re: Awesome 3.5 split different behaviour than in 3.4.15
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 describe is how it has always worked for me Gerald Klein DBA contac...@geraldklein.com www.geraldklein.com geraldklein.wordpress.com j...@zognet.com 708-599-0352 Arch/Gentoo Awesome, Ranger Vim the coding triple threat. Linux registered user #548580 *From:* Wojciech Daniło *Sent:* Tuesday, July 30, 2013 5:27 PM *To:* awesome@naquadah.org Hi! I've upgraded today awesome from 3.4.15 to 3.5.1 and noticed that the behaviour of awesome when using split layout changed. Lets imagine we have 3 windows (1 on the left and 2 on the right). In the old awesome while openning the fourth one it will apper on the right stack. In new awesome it appears on the left and thew one, which was on the left is moved to the right side. Is there any way to reverse this behaviour to the old one ?
Re: Awesome 3.5 split different behaviour than in 3.4.15
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 a default config? Marco signature.asc Description: Digital signature
Opening Apps On Screens
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 into another screen and tag and that's where vmware ended up. 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 I am using version v3.4.15 thanks for any help Gerald Klein DBA contac...@geraldklein.com www.geraldklein.com http://geraldklein.com/ geraldklein.wordpress.com j...@zognet.com 708-599-0352 Arch Awesome, Ranger Vim the coding triple threat. Linux registered user #548580
Re: Opening Apps On Screens
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 rules somewhere? It depends how you match the mplayer,
that's why I'm interested in seeing those. My suspicion is that you have the
mplayer being matched with rule_any and the vmplayer then gets matched as
well. You could have an exception there as in:
{ rule_any = { class = { mplayer2, mplayer } }
except = { class = vmplayer },
props = { tag = mytags[2][1] }
}
Or something similar. And then vmplayer wouldn't be matched by this rule.
Hope that it helps,
I.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Opening Apps On Screens
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,
-- maximized_vertical = false,
-- maximized_horizontal = false,
-- focus = true,
-- keys = clientkeys,
-- buttons = clientbuttons } },
properties = { border_width = beautiful.border_width,
maximized_vertical = false,
size_hints_honor = false,
maximized_horizontal = false,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = Kruler },
properties = { floating = true } },
{ rule = { class = Remmina },
properties = { floating = true } },
{ rule = { class = Gimp-2.6 },
properties = { floating = true, ontop = false } },
{ rule = { class = Gimp },
properties = { floating = true } },
{ rule = { class = xfce4-appfinder },
properties = { floating = true } },
{ rule = { class = Xfce4-appfinder },
properties = { floating = true } },
{ rule = { class = Kcalc },
properties = { floating = true } },
{ rule = { class = toolbox },
properties = { floating = true } },
{ rule = { class = Shutter },
properties = { floating = true } },
{ rule = { class = MPlayer },
properties = { tag = tags[2][1] } },
{ rule = { class = mplayer },
properties = { tag = tags[2][1] } },
{ rule = { class = feh },
properties = { tag = tags[1][1] } },
{ rule = { class = Feh },
properties = { tag = tags[1][1] } },
{ rule = { class = vdpau },
properties = { tag = tags[1][1] } },
{ rule = { class = Conky },
properties = {
tag = tags[2][1],
floating = true,
sticky = true,
ontop = false,
focusable = false,
size_hints = {program_position, program_size}
} },
--{ rule = { class = Htop },
-- properties = { tag = tags[3][10] } },
-- Set Firefox to always map on tags number 1 of screen 2 (3)?
--{ rule = { class = Firefox },
-- properties = { tag = tags[3][1] } },
}
-
Gerald Klein DBA
contac...@geraldklein.com
www.geraldklein.com
geraldklein.wordpress.com
j...@zognet.com
708-599-0352
Arch/Gentoo Awesome, Ranger Vim the coding triple threat.
Linux registered user #548580
From: Ignas Anikevičius
Sent: Wednesday, July 31, 2013 9:20 AM
To: awesome@naquadah.org
Cc: Gerald Klein
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 rules somewhere? It depends how you match the mplayer,
that's why I'm interested in seeing those. My suspicion is that you have the
mplayer being matched with rule_any and the vmplayer then gets matched as
well. You could have an exception there as in:
{ rule_any = { class = { mplayer2, mplayer } }
except = { class = vmplayer },
props = { tag = mytags[2][1] }
}
Or something similar. And then vmplayer wouldn't be matched by this rule.
Hope that it helps,
I.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
