-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client disappears when sending to screen #83
Comments
Do you have a selected tag on the second screen? If not, create one, select it and try again. |
No I don't. I use a combination of volatile and exclusive tags. I.e. I have a "www" tag on screen 2 for my browsers. When I move one of my browser clients to screen 1 then I expect a "www" tag there to be created. Any idea how I can accomplish that? Also, I think clients should never just disappear. They should always be added somewhere, or the client is effectively "lost". |
Clients disappear when they are not on the current desktop just like in every other WM. The problem is that you have no desktop/tag at all. We have a Untested: client.connect_signal("request::tag", function(c)
if #c.screen.tags == 0 then
awful.tag.add("New tag", {layout = awful.layouts.layouts[1]})
end
end) |
When I use Modkey+o to send a client to another screen (
c:move_to_screen()
) then the client window simply disappears. I have tried with every combination of:All using Tyrannical's
example.rc.lua
.I am pretty sure the bug is with Tyrannical somewhere. If I use Awesome's own default rc.lua (with the 9 tags) then moving clients between screens works fine.
The text was updated successfully, but these errors were encountered: