On Fri, Feb 26, 2016 at 12:04 AM Eric Snow wrote:
> On Wed, Feb 24, 2016 at 11:26 PM, Andrew Wilkins
> wrote:
> > Howdy,
> >
> > Occasionally I'll change a test, and some string equality test will fail
> > with a wall of text. Sometimes we
I agree with Horacio, you're my hero, Andrew.
I was actually just looking at sergi's diffmatchpatch implementation for
exactly this purpose a couple days ago. Thanks for doing that!
On Thu, Feb 25, 2016 at 6:09 AM Andrew Wilkins
wrote:
> On Thu, Feb 25, 2016 at
On Thu, Feb 25, 2016 at 5:23 PM roger peppe wrote:
> Nice. FWIW I have a related tool that tries to help find where a regexp
> mismatch has happened. It parses the output of gocheck, so it's
> probably not that useful to non-acme users but you might want
> to consider
Nice. FWIW I have a related tool that tries to help find where a regexp
mismatch has happened. It parses the output of gocheck, so it's
probably not that useful to non-acme users but you might want
to consider including the approach (http://paste.ubuntu.com/15195795/)
for fancycheck.Matches and
You are my new personal hero
On Thursday, 25 February 2016, Andrew Wilkins
wrote:
> Howdy,
>
> Occasionally I'll change a test, and some string equality test will fail
> with a wall of text. Sometimes we shouldn't be checking the whole string,
> but sometimes it's
Howdy,
Occasionally I'll change a test, and some string equality test will fail
with a wall of text. Sometimes we shouldn't be checking the whole string,
but sometimes it's legitimate to do so, and it can be difficult/tedious to
spot the differences.
I've just written a checker which diffs the