You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a configuration option specifying something like horizontal_order: right_to_left, vertical_order: down_to_up, assignment_order: horizontal_then_vertical
why
Simple answer: to make visual feedback unnecessary more often, to make more actions doable by muscle memory.
I want, when doing a split, for the bottom-most window to keep its shortcut key. I am most frequently visiting bottom-most windows, and upper windows are more supplementary/temporary, so I would prefer for the bottom-most windows to keep the same keys, so that I can visit them by muscle-memory.
Currently, with top-down naming, creating a new split in one column or the other, makes the bottom-most window's shortcut key change.
Additionally, currently, after creating a new split in the leftmost column, the bottom-most column of the right column will be renamed. I would prefer that bottom-most windows not be renamed due to creating upper windows.
more
If it's not too difficult, it would be better, I think, if creating a row in left column did not rename items in right column, and vice-versa. I generally only have a left and right vertical split, and I would prefer if splitting these horizontally didn't really interfere with each other's shortcut assignment.
I never have more than 2 vertical columns (except that some h-split might be further-split vertically - but these are not root-level vertical columns). All of this might differently be described as "give 2 vertical columns their own namespace, with their own designated shortcut keys, and allow for down_to_up naming order".
The text was updated successfully, but these errors were encountered:
ipsod
changed the title
Feature Request: reverse vertical naming order
Feature Request: customizable key assignment order
Oct 31, 2022
what
a configuration option specifying something like
horizontal_order: right_to_left
,vertical_order: down_to_up
,assignment_order: horizontal_then_vertical
why
Simple answer: to make visual feedback unnecessary more often, to make more actions doable by muscle memory.
I want, when doing a split, for the bottom-most window to keep its shortcut key. I am most frequently visiting bottom-most windows, and upper windows are more supplementary/temporary, so I would prefer for the bottom-most windows to keep the same keys, so that I can visit them by muscle-memory.
Currently, with top-down naming, creating a new split in one column or the other, makes the bottom-most window's shortcut key change.
Additionally, currently, after creating a new split in the leftmost column, the bottom-most column of the right column will be renamed. I would prefer that bottom-most windows not be renamed due to creating upper windows.
more
If it's not too difficult, it would be better, I think, if creating a row in left column did not rename items in right column, and vice-versa. I generally only have a left and right vertical split, and I would prefer if splitting these horizontally didn't really interfere with each other's shortcut assignment.
I never have more than 2 vertical columns (except that some h-split might be further-split vertically - but these are not root-level vertical columns). All of this might differently be described as "give 2 vertical columns their own namespace, with their own designated shortcut keys, and allow for down_to_up naming order".
The text was updated successfully, but these errors were encountered: