On Wed, Dec 9, 2020 at 11:11 AM Jeff King <peff@xxxxxxxx> wrote: > > On Wed, Dec 09, 2020 at 12:55:35AM -0600, Felipe Contreras wrote: > > > After investigating alternatives for exrc I found too many, doing a wide > > range of irrelevant stuff, many unmaintained, others requiring multiple > > dependencies, and some loaded the configuration too late. > > I'm not opposed to this solution, but I probably wouldn't use it myself. > I wonder if it would be sufficient to just say "here are some sensible > vim options", coupled with human-readable instructions for how to > integrate them into your .vimrc, along with some path-selection. > > It's perhaps not quite as turnkey. On the other hand, it's easy for > people who are even moderate vim users to understand what each line > does. In the plugin solution, there are more lines dedicated to loading > the config than there are actual config lines. If they only code for Git, it's straightforward to tell them how to configure vim. But if the user contributes to two projects with two different code-styles it gets to get tricky to tell them what to do. And when you get to three, my bet is that the vast majority of people wouldn't know what's the best solution for the user. This is the most non-intrusive solution. Cheers. -- Felipe Contreras
