Splits and `:tabedit` do not work nicely with each other / do not have vim behavior
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
It looks like :tabedit and the splits (:split and :vsplit) do not work so nicely together.
If I am right:
- in vim,
:tabeditopens tabs, and then within the tab it is possible to open as many splits as wanted. By doinggtorgT, one moves between tabs, each containing all the corresponding splits. This is convenient, as I can have a tab for fixing something, another for working on another issue, etc.
By contrast here:
-
using
gt/Tfor moving between tabs move only the tab in the current split. I.e., we have a split of tabs, rather than a tab of splits. -
combined with https://github.com/VSCodeVim/Vim/issues/4745 I think this leads to behaviors that are quite unlike vim (?).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior in VS Code using :tabedit, :split, :vsplit, and gt/gT, then inspect the extension's tab and split handling. Compare the current behavior with Vim's tab-of-splits model and the related issue #4745. Done means tab navigation preserves the expected group of splits and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100