David Barnett

I also noticed maktaba doesn't shout warning and error logging to the user as messages come in (#185). That part should be pretty easy to make built-in.

Yep, I thought maybe an explicit `@public`, `@dict dict.fn` or `@function dict.fn` might help, but I tried some variations on that and didn't see any existing workaround either. Looks like...

Just checking in, have you gotten any further with making this case work? Are you still interested in contributing a fix? I agree there's no reason to skip functions that...

Now you mention it, plugins with most of the logic in python might benefit from some instrumentation to collect doc comments from the python too. You are correct that most...

This may be less of an issue once #24 ('main file' requirement) and #25 (extra crawl paths) are resolved.

Yep, adding them into addon-info.json is one option I'm considering. The downsides are they would be non-standard extensions to the spec, this isn't something we'd ever want to access at...

…but would confuse vim's help file syntax highlighting. And if the default is a strange literal expression, like `[1, 2, 3]`, or an English phrase like "the file being edited",...

Hi, thanks for getting involved! Could you clarify: does this change improve something, or were you just tinkering with the files?

Vimdoc also has a side-effecty architecture that makes several of its existing limitations hard to solve. Separating the logic out into a parsing phase that builds a traversable model of...

And I guess independent of refactoring, we'll want integration tests that say "given this example plugin, vimdoc should produce output containing X, Y, and Z".