David Barnett

Oh, I wasn't getting how python package dependencies were relevant until I saw the specific example with coverage. But are you imagining cases where there's no system-wide install of python...

Looks like another option would be to run `poetry shell` or `source $(poetry env info --path)/bin/activate` in the terminal before starting vim. Or you could set up an autocmd to...

Looks like vim added some built-in functions for working with signs in 8.1.0614 (see vim/vim#3652 and `:h sign-functions-details`), so this would be a polyfill around those and follow conventions from...

Looking around for existing instant/ files, I found a couple interesting cases besides flags.vim: * Pre-configuring default settings for vim that can be overridden later in vimrc. May need to...

And since this will require a plugin-by-plugin migration process, I'd want users to be able to easily report issues to plugin maintainers and have an escape hatch to re-enable the...

A better error would say something like `Invalid flag "plugin" for plugin "someplugin": Expected a dictionary. Got a number.`.

Fair point, might as well accommodate those (and then bump maktaba's version so you could reliably depend on it).

In terms of whether to check rtp and throw an error, I can see pros and cons either way. If we don't check rtp, it'll be a little weird sourcing...

The Glaive autocomplete should check each plugin for flags and filter out the plugins that don't expose any. Our plugin manager story means that we can't count on plugins being...

Yep, that's partially because we didn't nail down the division of labor very well from the start. My goal is to fix it to _not_ impose plugin management on anyone....