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
The default keybindings on Windows, Linux and BSD for navigating splits and tabs are the same, meaning that it's not possible to actually navigate them without re-binding them in the config.
On Mac, we have:
Action
Key
Move to next tab
Control + Tab OR Command + Shift + ]
Move to previous tab
Control + Shift + Tab OR Command + Shift + [
Select next split
Command + ]
Select previous split
Command + [
So, different keybinds for navigating tabs and splits.
On Windows, Linux, and BSD, we have:
Action
Key
Move to next tab
Control + Tab OR Control + Shift + ]
Move to previous tab
Control + Shift + Tab OR Control + Shift + [
Select next split
Control + Shift + ]
Select previous split
Control + Shift + [
So, the same keybinds for next tab and next split, and similarly for previous. Meaning that it's impossible to select the next split without re-binding the keys, or doing a weird "move to next split AND tab, then move to prev tab" motion, which is obviously undesirable.
Not sure what the default keybindings should be to avoid clashing with potential keybindings in terminal editors, but perhaps either:
Removing the redundant keybindings for tab navigation, so that we'd be left with Ctrl + Tab for tabs and Ctrl + Shift + ] for splits;
Or, using square brackets for one, and angled brackets for the other
The text was updated successfully, but these errors were encountered:
The default keybindings on Windows, Linux and BSD for navigating splits and tabs are the same, meaning that it's not possible to actually navigate them without re-binding them in the config.
On Mac, we have:
Control + Tab
ORCommand + Shift + ]
Control + Shift + Tab
ORCommand + Shift + [
Command + ]
Command + [
So, different keybinds for navigating tabs and splits.
On Windows, Linux, and BSD, we have:
Control + Tab
ORControl + Shift + ]
Control + Shift + Tab
ORControl + Shift + [
Control + Shift + ]
Control + Shift + [
So, the same keybinds for next tab and next split, and similarly for previous. Meaning that it's impossible to select the next split without re-binding the keys, or doing a weird "move to next split AND tab, then move to prev tab" motion, which is obviously undesirable.
Not sure what the default keybindings should be to avoid clashing with potential keybindings in terminal editors, but perhaps either:
The text was updated successfully, but these errors were encountered: