Re: [PATCH v2 1/2] Add project-wide .vimrc configuration

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Dec 15, 2020, 03:03 UTC
Message-ID: <5fd8279ce0696_d7c482087@natae.notmuch>
In-Reply-To: <X9gT57SAHzGm3ET2@coredump.intra.peff.net>

Jeff King wrote:

> On Fri, Dec 11, 2020 at 02:56:22AM +0000, brian m. carlson wrote:

Show 11 quoted lines

>   - it doesn't suggest any actions that might be bad practices. I agree
>     that the instructions for auto-loading this .vimrc are more
>     complicated than necessary and might have security implications.
>     Carrying a file in contrib/vim that says "copy this to ~/.vim/foo"
>     or even "copy these lines to your ~/.vimrc" seems a lot safer. And
>     it makes it easier for people who prefer to adapt the config to
>     their own setup.
> 
> So I'm not opposed to carrying some vim config, but I think it's best to
> focus on simplicity and providing human-readable instructions, rather
> than ad-hoc plugin infrastructure.

Generally I would agree, but do you know what such instructions would look like?

In particular what instructions would look like for a person that contributes to more than 3 projects with different C code-style.

I can assure they are anything but human-readable.

Cheers.

-- 
Felipe Contreras