sagb
sagb
The bug is still here in Debian testing (bullseye)
Force push drops non-relevant commit.
What do you expect, after all, when pressing Alt-Tab in chrome? Both programs try to consume the event, which one should "win"? Not surprising, that one of them fails in...
Does using another keyboard combination in alttab -or- disabling alt-tab in chrome solve the problem?
If I used chrome, I would try to disable alt-tab shortcut in chrome, because it should not be web browser task. For now I won't fix this, but hints are...
I have no idea why.
Probably a nice feature. I have no time for this, patches are welcomed.
Probably a compositor can do everything on its own: https://confluence.jaytaala.com/display/TKB/My+Manjaro+i3+setup#MyManjaroi3setup-Ricingalttab
Let's clarify: when you run `alttab -d 1`, and switch from window A belonging to desktop D(A) to window B belonging to another desktop D(B), window A is left in...
This looks reasonable, I plan to rewrite options syntax at ~1.4 resease. For now, I just make `-d 3` exclude special desktop too.