David Barnett

Yeah, symlink looks like a decent workaround, and the plugin could have an explicit way to configure the path to the bazel executable. Note I recently added 7d816323aa for a...

My big question is will neomake support all the functionality we'll ultimately want? I admit I may just not understand how to use it properly, but I found a lot...

An interactive terminal view isn't necessarily a "must", but looks straightforward to implement in vim 8 at least. I think we'd want some kind of "view log" operation if we...

> An interactive terminal view isn't necessarily a "must", but looks straightforward to implement in vim 8 at least. >> It doesn't look straightforward to me at all. Could you...

Minimal repro: ``` vim function ThrowBoom() abort throw 'BOOM' endfunction function ReproNotReallySilent() abort call ThrowBoom() try call join(1) catch /E714:/ endtry endfunction ``` `:silent! call ReproNotReallySilent()` The docs on error...

Reopening to track cleanup. We should change it to shout an error after a couple weeks, and then remove it entirely about a month after that.

We could make `maktaba#plugin#Detect` and `maktaba#plugin#Enter` be the only things that automatically trigger sourcing instant files, and have an explicit function to do the maktaba initialization (steps 3–5, including initial...

Also, `GetOrInstall` is a partial workaround for these problems: It handles checking if the plugin already exists in a way that doesn't trigger instant files early. But the behavior is...

Yeah, looks like it!

@Kashomon I'm filing this to follow up on what was a TODO in the code, but I suspect we don't want to handle those values specially since I don't think...