Open patrikkj opened 1 month ago
How should more complicated layouts work in this case?
h_tiles
window1
v_tiles
window2
window3
window4
I think an angle-based heuristic could make sense:
Regular in-order tree traversal using next
and previous
could also go a long way, eg. win1 -> win2 -> win3 -> win4
in your example.
I would also like to have this feature :)
Would love this option as well. In many cases I have 2, maybe 3 windows.
The complex layout options is when hjkl works better, but for 90% of the time I basically want "some other" window of which is either one or two windows.
Given AeroSpace tree nature, a more well-defined algorithm would be to add possibility to focus next/prev window in DFS (Depth-first search) order
For simple layouts, it will work exactly as clockwise/counterclockwise
But it's yet unclear how to make it work with move
and join-with
commands (maybe it's not needed)
Though next-dfs
/prev-dfs
works good with upcoming swap
command #8
Thank you for building a great tool!
One thing that I've missed is the ability to
focus
,move
andjoin-with
using clockwise/counterclockwise navigation, akin tomod1 + j
,mod1 + k
etc. in Amethyst. Alternative names could benext
/previous
.Features:
Example:
navigating to
window_3
in this case requires two actions,right
which would take you towindow_2
followed bydown
. This could have been done using a single ccw action.