David Barnett

Also warnings. The fact that we don't have line number for warnings combined with the fact that we show a few spurious warnings (e.g., for functions with multiple `@usage`s) means...

Agreed, looks like a bug that those are wrapping. Literal blocks _are_ supported but apparently don't override the normal text wrapping. As a workaround, consider just using line continuations and...

I did a little poking around here and it doesn't look too promising so far. It seems to parse *expressions* only, not commands, and doesn't seem to handle comments or...

I did find that https://github.com/vim-jp/vim-vimlparser does a pretty good job parsing arbitrary vimscript. We'd probably want to use that instead, but I can't figure out how to declare a dependency...

Another detail: Some tags might come at the top and apply to the whole section, but vim help files sometimes just drop tags inline in the middle of the prose....

@wsdjeg was interested in this for SpaceVim. I expect it would be straightforward to implement, with one gotcha that there's no markdown spec. I'd be interested in supporting both GFM...

Wow, I knew it would be tricky, but hadn't considered some of these bright red gotchas. Particularly the cases where we already know an arg value is safe, to always...

Yeah, that was intentional but not really ideal (and your workaround is the approach I intended to take until we come up with something better). We need a way to...

Bob mentioned to me that javadoc uses `@inheritDoc` for this exact case, so I propose we use that name. Example: ``` VImL "" " @section Configuration, config " @inheritDoc "...

Calling `@inheritDoc` support an enhancement instead of a bug. LMK if you disagree.