Malcolm Rowe

Right, if we can't tell, then assume that the feature is present.

I ran into this again today, while working on #103. We now have several occurrences of the "if found errors, `setqflist()`, else leave alone" pattern in various formatters. Even if...

That's... annoyingly quick, as deprecations go. I think we might want to basically replicate the functionality from https://github.com/dart-lang/dart-vim-plugin/pull/125, which checks whether `dart` exists, then does a version match on the...

Raised as vim/vim#538. Bizarrely it seems that the behaviour of `:silent!` is as we expect when an exception is thrown from a builtin function, just not when it's thrown from...

I'm guessing the proposal in #243 would make this obsolete?

Yes, fzf.vim adding an adding an `addon-info.json` would fix this specific case. In general: sounds like that uniquifying the plugin name _might_ work. It would mean that `maktaba#plugin#Get()` would be...

That sounds reasonable, I _think_. Certainly I agree with the principle that non-Maktaba-using plugins shouldn't conflict with anything, if possible. (Also, we can add `maktaba#extension#GetRegistry(name)` as an example of something...

For running the right Python, this might be able to be worked around with a `~/bin/python` (or whatever) in your `PATH` (or making the command overridable inside Maktaba, yes). However,...

A logging plugin would certainly be nice, but I was thinking of something that would be available to someone just using Maktaba. I like the idea of providing _something_ simple....

I actually wrote a very simple version of this (`throws` propagation with call-graph analysis) for google/vim-maktaba#110 (see corp CL 83011828 for generators and output). Some examples of the problems I...