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
When configuring keybinds, the direction parameters for new_split and goto_split are inconsistent:
new_split uses: up | down | left | right
goto_split uses: previous | next | top | left | bottom | right
The goto_split direction parameters include top and bottom, which can be misleading as they might imply focusing on the topmost or bottommost split in the layout, rather than simply moving to an adjacent split. This inconsistency with new_split (up and down) may confuse users and create ambiguity in the configuration.
Renames the top/bottom directions of `goto_split` to up/down. I have
tested this on linux (nixos) but given that `goto_split` is broken on
linux anyway (#2866) there's not a whole lot to test.
I have no way to build on macOS so I can't verify that I've changed
everything correctly for that.
Closes#3237
Description
When configuring keybinds, the direction parameters for
new_split
andgoto_split
are inconsistent:new_split
uses:up | down | left | right
goto_split
uses:previous | next | top | left | bottom | right
The goto_split direction parameters include top and bottom, which can be misleading as they might imply focusing on the topmost or bottommost split in the layout, rather than simply moving to an adjacent split. This inconsistency with new_split (up and down) may confuse users and create ambiguity in the configuration.
Steps to Reproduce
new_split
keybinds:goto_split
keybinds:Expected Behavior
The direction parameters should be consistent across both actions.
Actual Behavior
new_split
andgoto_split
use different sets of direction parameters.Suggested Change
Standardize the direction parameters to a single set, such as
previous | next | up | left | down | right
.This would improve clarity and ease of configuration.
The text was updated successfully, but these errors were encountered: