goto_split by number

[zachvalenta]

Maybe I'm just used to how iTerm does it:

but I think this paradigm is worthwhile in addition to the existing ghostty approach of goto_split:$DIRECTION. Feels like a lot of new users might also be used to the numeric approach from browser tabs. You can set up VS Code to work this way as well:

{ "key": "cmd+1", "command": "workbench.action.openEditorAtIndex1" },
{ "key": "cmd+2", "command": "workbench.action.openEditorAtIndex2" },
{ "key": "cmd+3", "command": "workbench.action.openEditorAtIndex3" },
{ "key": "cmd+4", "command": "workbench.action.openEditorAtIndex4" },
{ "key": "cmd+5", "command": "workbench.action.openEditorAtIndex5" },
{ "key": "cmd+6", "command": "workbench.action.openEditorAtIndex6" },
{ "key": "cmd+7", "command": "workbench.action.openEditorAtIndex7" },
{ "key": "cmd+8", "command": "workbench.action.openEditorAtIndex8" },
{ "key": "cmd+9", "command": "workbench.action.lastEditorInGroup" },

[pluiedev]

We don't really even give numbers to splits internally and everything is just modelled by a binary tree where it's easy to move in terms of the four cardinal directions, but as things stand this feature is not easy to implement.

[zachvalenta]

Another possible advantage of adding the by-numbers approach: let's say you have 4 panes. Getting from top L to bottom R is two keystrokes vs. a single (cmd+4) keystroke. Or: ease of pane navigation is a negative regression to the number of panes if you only have vim char|line-wise navigation.