Vimscript support
Open
Nobody has claimed this yet.
area/vimrc
kind/feature
size/L
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Is your feature request related to a problem? Please describe.
Many vimers have their own vimscripts in the ${HOME}/.vimrc, so it's better we can import or write some vimscripts in this extension.
Describe the solution you'd like
Some where in the user settings of this extension to write my own vimscripts.
Describe alternatives you've considered
Noop.
Additional context
No.
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. Begin by tracing where this extension reads user settings, then establish the intended import or writing scope for vimscripts and define what behavior will count as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, 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