-
Notifications
You must be signed in to change notification settings - Fork 109
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
Any way to get element on 'right' or 'left' of a given element? #207
Comments
I figured how to implement it. It was hard and annoying, so for the record here is the code: https://gist.github.com/omenius/36002dc4dc699016b11c71f7a956c02a The I think this is how i3 should work natively. There is a reason why most tiling managers have no tabs. Imo using tabs destroys the workflow if you don't have separate keybinds for cycling through the tabs and moving between not tabbed windows. |
So let's say we have a window, for example:
window = i3.get_tree().find_focused()
Now I'd like to know the .right and .left items relative to our window (if those windows exist anyway).
Meaning the windows where user would end up when invoking
i3-msg focus right
ori3-msg focus left
I'm sure there must be some way to deduce the .right and .left items, but it's beyond my limited imagination.
Why?
If you are familiar with the examples/focus-next-visible.py, I'm kind of trying to create a focus-right/left-visible.py.
I want to be able to navigate through tabbed containers without switching the visible tab, using the i3 movement keys. I have separate keybind for cycling through the tabs. I really love it like this.
Here you can see hacky interpretation of how I like it. It gets around the issue by simply trying out and navigating back when it opens a tab that was not visible to user. It's slow as pope and flickers like damn.
The text was updated successfully, but these errors were encountered: