From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
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>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: [PATCH v2 0/2] vim: configuration and sharness syntax
Date: Wed, 9 Dec 2020 00:55:35 -0600 [thread overview]
Message-ID: <20201209065537.48802-1-felipe.contreras@gmail.com> (raw)
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.
The only one that seemed to fit the bill is vim-addon-local-vimrc, which
does work straightofrwardly, but hasn't been updated since 2015.
Instead I chose to simply vim-addon-local-vimrc, and take advantage of
git ('git rev-parse --show-toplevel' saves us a lot of the complexity of
these loaders).
The result is a very simple loader which is also secure, since it cannot
do anything unless you manually whitelist the project(s) you want load
.vimrc files from.
And since I already created some files in 'contrib/vim' I decided to put
the sharness syntax file there too.
Felipe Contreras (2):
Add project-wide .vimrc configuration
contrib: vim: add sharness syntax file
.vimrc | 23 ++++++++++++++++++++++
contrib/vim/plugin/gitvimrc.vim | 21 ++++++++++++++++++++
contrib/vim/syntax/sharness.vim | 34 +++++++++++++++++++++++++++++++++
3 files changed, 78 insertions(+)
create mode 100644 .vimrc
create mode 100644 contrib/vim/plugin/gitvimrc.vim
create mode 100644 contrib/vim/syntax/sharness.vim
--
2.29.2
next reply other threads:[~2020-12-09 6:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 6:55 Felipe Contreras [this message]
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 ` [PATCH v2 0/2] vim: configuration and sharness syntax Jeff King
2020-12-10 3:25 ` 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=20201209065537.48802-1-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=aaron@schrab.com \
--cc=christian.couder@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=liu.denton@gmail.com \
--cc=peff@peff.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.