From: Jeff King <peff@peff.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Emily Shaffer <emilyshaffer@google.com>,
"Brian M. Carlson" <sandals@crustytoothpaste.net>,
Aaron Schrab <aaron@schrab.com>,
Denton Liu <liu.denton@gmail.com>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: [PATCH v2 0/2] vim: configuration and sharness syntax
Date: Wed, 9 Dec 2020 12:11:48 -0500 [thread overview]
Message-ID: <X9EFVIlm8sYKtLwr@coredump.intra.peff.net> (raw)
In-Reply-To: <20201209065537.48802-1-felipe.contreras@gmail.com>
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.
I dunno.
> And since I already created some files in 'contrib/vim' I decided to put
> the sharness syntax file there too.
This part I like very much. The actual policy logic is sufficiently
complex that I hope people will be able to contribute back small fixes.
-Peff
next prev parent reply other threads:[~2020-12-09 17:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 6:55 [PATCH v2 0/2] vim: configuration and sharness syntax Felipe Contreras
2020-12-09 6:55 ` [PATCH v2 1/2] Add project-wide .vimrc configuration Felipe Contreras
2020-12-09 8:53 ` Christian Brabandt
2020-12-09 10:29 ` Felipe Contreras
2020-12-09 10:45 ` Christian Brabandt
2020-12-09 17:27 ` Jeff King
2020-12-10 1:55 ` Felipe Contreras
2020-12-10 15:27 ` Jeff King
2020-12-11 0:43 ` Felipe Contreras
2020-12-10 3:50 ` brian m. carlson
2020-12-11 1:08 ` Felipe Contreras
2020-12-11 2:56 ` brian m. carlson
2020-12-11 4:37 ` Felipe Contreras
2020-12-15 1:39 ` Jeff King
2020-12-15 3:03 ` Felipe Contreras
2020-12-15 5:28 ` Jeff King
2020-12-15 6:56 ` Felipe Contreras
2020-12-09 6:55 ` [PATCH v2 2/2] contrib: vim: add sharness syntax file Felipe Contreras
2020-12-09 7:05 ` Eric Sunshine
2020-12-09 10:39 ` Felipe Contreras
2020-12-09 17:11 ` Jeff King [this message]
2020-12-10 3:25 ` [PATCH v2 0/2] vim: configuration and sharness syntax Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X9EFVIlm8sYKtLwr@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=aaron@schrab.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).