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
Fix multiple window movement issue #5521
base: next
Are you sure you want to change the base?
Conversation
860c930
to
9ccff4c
Compare
db6dc2b
to
ff7be20
Compare
98978e1
to
07bf19d
Compare
5ac043e
to
6f2a85b
Compare
Converted to a draft since it depends on #5529 |
@slyshot please rebase onto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your pull request.
Since this is a purely behavioral change, we will need some tests that cover this behavior. Let me know if you need help with them.
Will this be merged? I've been using patch ever since it came out and everything performs like it should. |
This solves #5382. The issue is caused because there's no container between the workspace and the windows, and when focus is moved up to the workspace,
tree_move
will refuse to move workspaces.I was planning on making a change elsewhere(Making the split container if they'd otherwise attach to the workspace at all), but as I mentioned in my comment on the issue, the windows attaching directly to the workspace seems specifically intentional based on comments in code. For this reason, making the change at
tree_move
instead of earlier seems needed to respect that intention. If I'm mistaken in any way, or making the earlier change seems like a good idea anyways, let me know.Thanks.