Ability to define custom ex commands
Nobody has claimed this yet.
- 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.
I use neovim integration, but I am unable to define the custom ex commands I use in neovim, and the commands defined in my ~/.config/nvim/init.vim are not respected. To give you a flavour, these are the ones I currently have defined for neovim:
command! W :w
command! Wa :wa
command! Wq :wq
command! Wqa :wqa
command! E :e
Describe the solution you'd like
I am able to define custom ex commands either in VSCode settings.json or have the ones in my neovim config respected.
Describe alternatives you've considered
Additional context
I'd be happy to have a go at implemeting this myself if this is something you'd accept a PR on and someone could point me in the right direction.
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 by reviewing how the extension reads VS Code settings.json and how it handles the user's ~/.config/nvim/init.vim. Compare those paths with the existing custom ex-command integration points, if any. Done means users can define custom ex commands in settings.json or have the listed Neovim commands respected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100