Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can not detect correct focused workspace without using i3 specific command. #2921
Binary i3 version: 4.14-3-g7251553
What I did and saw:
+Dragging a window from workspace A to B on a multi-monitors setup.
What I expected instead:
"wmctrl -d" correctly see B as the focused workspace.
The tint2 panel also appear to incorrectly recognized the focused workspace, just like wmctrl. That is why I suspect it is i3 fault.
When using workspace back and forth feature nothing happen. I3 stuck to B and wmctrl stuck to A.
I have to switch to another workspace C, or focus the workspace B again (shortcut or i3-msg workspace B or wmctrl), then everything back to normal.
Base on the above behaviour, I use the following script to bypass this quirk for now, in case anyone need it