Check missing/added Ex commands in neovim *by script*

Open
#123 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
vim
Domain
tooling

Research direction

Start with s:VimLParser.neovim_additional_commands and s:VimLParser.neovim_removed_commands, then read the referenced discussion about nvim_get_commands and its non-builtin limitation. Define how a script should diff the available command list against these manually maintained lists; done means the comparison can be run by script and its results are usable for updating the lists.

Written by the indexing model from the issue text.

Description

Currently

  • s:VimLParser.neovim_additional_commands
  • s:VimLParser.neovim_removed_commands

is managed manually.
neovim supports nvim_get_commands() listing available commands.

So it can automate by adding script diffing command list.

Ref

https://github.com/vim-jp/vim-vimlparser/issues/118#issuecomment-513278223

However, nvim_get_commands exists already (although only for non-builtin). Might be useful in general, but only for "dynamic" linting/parsing (i.e. not for vint, vimlparser.py etc, which need the list already).

Dominant language
Vim Script
Stars
173
Forks
28
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vim-jp/vim-vimlparser

All issues in vim-jp/vim-vimlparser

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.