Scott Baker

A while back I added [unified diff support](https://github.com/so-fancy/diff-so-fancy#with-diff). Anything that can output unified diffs will probably work with d-s-f. Our primary focus, as @OJFord said is `git` as that is...

I (@scottchiefbaker) maintain the Perl code and handle the GitHub releases. Other people work on the `npm` versions and specific packages versions. Looks like in this case there was a...

Several of the things you fixed are already fixed on `next`. All PR should be based against that branch. Can you redo this PR to target the [correct branch](https://github.com/so-fancy/diff-so-fancy#contributing).

I've been hemming and hawing over this issue for a while. Personally I don't think I would use, but I can definitely some people in the community wanting it. The...

@ericbn I just landed some commits to handle caching of `git_config()` that might speed things up a bit. They're on `next` take a look and we can build from there.

@ericbn I updated #278 with some more details. If we can get that figured out, landing this will be a no-brainer.

@ericbn I'm circling back to this now that I got our startup issues figured out. I removed the `Encode` module all together because it was slowing down startup. I see...

Does this kick in if there is a commit line, or all the time? Seems like this is a `git show` thing, not a `git diff`?

@ericbn thanks for bringing this back up... It slipped off my radar. Ultimately I think it boils down to "do our users want this". It adds two additional lines to...

This is a valid issue. I hadn't really considered the use case where git is not installed at all. I will ponder this today.