Come up with way to designate parts of a .vimrc as VSCodeVim-only or Vim-only
Open
Nobody has claimed this yet.
area/vimrc
kind/enhancement
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
We'd like for people to be able to use the same .vimrc between VSCodeVim and real (neo)vim. However, for various reasons there may be a need to designate certain parts of the .vimrc as VSCode-only or as Vim-only.
As suggested here, we could do something like:
if has("vscode")
" Some rules
endif
or maybe a comment with a special incantation.
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
No files, tests, or entry points are named. Start by reviewing the proposed has("vscode") condition and the alternative special-comment approach, then identify the extension's configuration handling; done should mean a documented, tested way to separate VSCodeVim-only and Vim-only sections of a shared .vimrc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim, vim, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100