David Barnett
David Barnett
If vimdoc directives are above the first `@usage` line in a doc comment block with multiple `@usage`s, they only apply to the first `@usage`. For instance, given: ``` VimL ""...
The documentation says vimdoc supports multiple `@usage` directives on the same command or function. This does work for very simple cases, but has quite a few bugs. Attempting to link...
There should be a way to document individual mappings so they're listed in the mappings section of help files. We should probably just have an explicit `@mapping KEYS [mode]` rather...
It's easy to get confused and write `@function(name())` in vimdoc since the doc tag includes parentheses (`name()` vs `name`). We should consider accepting `@function(name())` as equivalent to `@function(name)`. Note this...
For some plugins, there's no natural place to put doc comments like `@section` blocks to control vimdoc output, so we've resorted to a convention of adding empty `plugin/doc.vim` files purely...
In keeping with the spirit of DRY, it'd be nice if vimdoc could understand maktaba's variable type checking. Whenever `maktaba#ensure` calls are present for `a:foo`, it could add some (optional)...
I noticed that if I set up a rule to star a thread, it adds a star to *every* matching message in the thread. This is usually not the behavior...
The suggested filters to hook up to Gmail Automata will temporarily archive all unprocessed threads, something like: `Matches: from:([email protected]) -in:chats -{label:mute} Do this: Skip Inbox` That means even if a...
When matching on the subject, I found that "Re:" and "Fwd:" prefixes in the subject can mess up the match for a rule that would otherwise match. For example: Rule:...
How do you run the tests? In particular, I'm looking for a way to quickly run the tests from the command line as I'm making changes.