David Barnett

`maktaba#system#Call` captures stdout and stderr output so vim plugins can process it programmatically, but that's only implemented for 'hidden' mode. It would be useful to be able to capture output...

Use library for vimscript parsing instead of regexes

3

Per neovim/neovim#170 and https://neovim.io/doc/user/api.html#nvim_parse_expression(), libnvim now offers an API to parse vimscript syntax to an AST. We should give it a shot hooking that up to vimdoc and see if...

For plugins with a lot of functions or flags, there doesn't seem to be a directive to tell vimdoc to group item docs into a subsection. For instance if I...

Add a markdown output mode

1

vimdoc should be able to generate markdown output as an alternative to vim helpfile syntax. We'll have to figure out how relative links can work first. Note: These wouldn't be...

The default documentation for a `plugin[mappings]` flag just says ``` Configures whether plugin/mappings.vim should be loaded. Default: 0 ``` It should also mention that it can accept string values, and...

If there's no plugin name declared in addon-info.json, vimdoc takes the name of the directory that contains the plugin as the plugin name. Often this directory will have a "vim-"...

Vimdoc can detect ``` vim call s:plugin.Flag('foo', 'bar') ``` but not ``` vim call s:plugin.Flag( \ 'foo', 'bar') ```

Vimdoc issues an ArgumentMismatch warning if actual function arguments don't match those declared in the doc block, but it's not checking command arguments at all. It should issue a warning...

Detect undeclared thrown errors

2

Vimdoc should detect undeclared thrown errors and either error out of doc generation or automatically document them. This would include explicit `throw` invocations and/or errors thrown by detected function calls,...

Would be cool if we had a logo to include in the docs and the deb. I'm assuming this would be some kind of a "V" with a scroll or...