Calculate & apply diff when syncing neovim state back to VSCode
Open
Nobody has claimed this yet.
area/neovim
area/performance
kind/refactor
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Currently we do a full-document copy, which is dumb.
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
Start in src/neovim/neovim.ts at the linked full-document copy around line 160, and trace how Neovim state is synced back to VSCode. Determine where the document diff should be calculated and applied instead of copied wholesale. Done means the sync uses a diff while preserving the existing state-sync behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, typescript, vscode
- Domain
- devtools, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100