Skip to content
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

Open
sandermarechal opened this issue Nov 30, 2017 · 4 comments
Open

Client disappears when sending to screen #83

sandermarechal opened this issue Nov 30, 2017 · 4 comments

Comments

@sandermarechal
Copy link

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:

  • Awesome 4.0 (Debian stable)
  • Awesome 4.2 (Debian testing)
  • Tyrannical 1.0.0
  • Tyrannical master

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.

@Elv13
Copy link
Owner

Elv13 commented Nov 30, 2017

Do you have a selected tag on the second screen? If not, create one, select it and try again.

@sandermarechal
Copy link
Author

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".

@Elv13
Copy link
Owner

Elv13 commented Dec 5, 2017

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 request::tag signal to all you need to listen to if you want to create a fallback tag.

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)

@sandermarechal
Copy link
Author

sandermarechal commented Dec 6, 2017

Thanks, I will try that.
Is there any way to have Tyrannical create the correct tag for the client using it's matching strategy, similar to the requests in #80 and #56?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants