From: Jeff King <peff@peff.net>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: New sharness/test vim syntax
Date: Tue, 8 Dec 2020 12:56:29 -0500 [thread overview]
Message-ID: <X8++TTnv95IAIkZL@coredump.intra.peff.net> (raw)
In-Reply-To: <CAMP44s1D-Zp3KDS+Hi74a=Lkc7Nc_0qiEzQEF0Pmj=bD8i+=JQ@mail.gmail.com>
On Thu, Nov 26, 2020 at 04:24:42AM -0600, Felipe Contreras wrote:
> It gets a bit tedious to see all the tests in the same color, so I
> wrote my own vim syntax file so that at least the body of
> test_expect_success is highlighted properly.
Thanks for sharing this. Over the years I've gotten used to the horrible
all-red view when editing our test scripts, but I'm looking forward to
leaving that behind. :)
-Peff
next prev parent reply other threads:[~2020-12-08 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 10:24 New sharness/test vim syntax Felipe Contreras
2020-12-08 17:56 ` Jeff King [this message]
2020-12-08 21:54 ` Emily Shaffer
2020-12-09 0:30 ` 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=X8++TTnv95IAIkZL@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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).