You are not logged in.
I have a problem:
I'm happily using Awesome 4.1, but when I launch some applications they get into a weird state.
When I open inkscape or (sometimes) claws-mail, for example, they start with up-and-down and left-and-right maximisation, which means they are not tiled:
Screenshot 1
If I press Meta+M, which should toggle maximise, the windows' symbol becomes a "+" and still refuses to behave:
Screenshot 2
I have this in my rc.lua, which I was hoping would avoid this problem, but it does not.
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
border_color = beautiful.border_normal,
focus = awful.client.focus.filter,
raise = true,
keys = clientkeys,
-- https://github.com/awesomeWM/awesome/blob/master/docs/90-FAQ.md --> Why some floating clients can not be tiled?
-- add the following two:
maximized_vertical = false,
maximized_horizontal = false,
floating = false,
buttons = clientbuttons,
screen = awful.screen.preferred,
placement = awful.placement.no_overlap+awful.placement.no_offscreen
}
},
-- Floating clients.
{ rule_any = {
instance = {
"DTA", -- Firefox addon DownThemAll.
"copyq", -- Includes session name in class.
},
class = {
"Arandr",
"Gpick",
"Kruler",
"MessageWin", -- kalarm.
"Sxiv",
"Wpa_gui",
"pinentry",
"veromix",
"xtightvncviewer"},
name = {
"Event Tester", -- xev.
},
role = {
"AlarmWindow", -- Thunderbird's calendar.
"pop-up", -- e.g. Google Chrome's (detached) Developer Tools.
}
}, properties = { floating = true }},
-- Add titlebars to normal clients and dialogs
{ rule_any = {type = { "normal", "dialog" }
}, properties = { titlebars_enabled = true }
},
-- Set Firefox to always map on the tag named "2" on screen 1.
{ rule = { class = "Firefox" },
properties = { screen = 1, tag = "2" } },
{ rule = { class = "Claws Mail" },
properties = { screen = 1, tag = "8" } },
}
-- }}}
Any ideas what state the windows are in, between left-right up-down or "+", or how I can avoid this state from happening?
Thanks!
Last edited by eodna (2017-05-10 10:58:32)
Offline
Hi,
I stumbled onto the same problem...
From my understanding, the "+" ist just a newer combined state for "maximized". The two variants with the arrows are "maximized-horizontal" and "maximized-vertical". You can look the meaning up in the AwesomeWM Documentation.
If you want to include it in your rc.lua, I'd suggest to include
maximized = false
in the rule regarding all clients.
I use a workaround in a regular terminal-window for getting the window-states usable again:
awesome-client 'for _,c in ipairs(client.get()) do
c.maximized = false;
c.maximized_horizontal = false;
c.maximized_vertical = false;
c.floating=false
end'
This sets all clients to not floating and not maximized in all three variants ("+", the two arrow-types). I'm sure, someone with a better understanding of Lua could modify it to target specific applications like Inkscape.
Offline
The
maximised=false
Does not seems to be respected, but your script does fix the misbehaving windows, which is great! Thanks a lot for that.
Any idea why the client initialisation rules are being avoided?
Offline
You're welcome.
Could be, that maximiSed is not being recognized. You could try maximiZed.
Offline
good guess, but in fact I had written "maximized" in rc.lua
Offline