Scott Baker

@OJFord we had to make some minor modifications to the library itself. Mainly to decrease startup time. Vanilla diff-highlight shells out to `git config` four times which really slows down...

@waldyrious if that is your complete git config then you have not set any diff-highlight specific colors. The defaults for the d-s-f version of diff-highlight are probably just different (we...

I just reverted the `diff-highlight` colors to the defaults... check out the latest on `next` and tell me if that addresses your issue. I probably just never should have tweaked...

OK try the `next` branch again... I think I got it respecting the diff-highlight defaults.

I cannot recreate this... Try clearing ALL the color options from both `~/.gitconfig` and `.git/config` and see if that resolves the problem? You can view the decoded ANSI codes with...

@waldyrious I updated the `ansi_reveal.pl` yesterday to show [REV/NOTREV](https://github.com/so-fancy/diff-so-fancy/commit/31cdf3f35f7ec9e9d9662aff1d0cee2c99744c65) after your first post Something is still setting bold but I have no idea what!

You're talking about vanilla diff? Not `git diff` output?

I've never used sub-modules. If you can submit a test case that adequately recreates this issue in a reliable and repeatable manner I can investigate this new feature..

I will investigate this now that I have some other stuff off my plate.

Can you explain `git config diff.renames copies`? I'm not familiar with that setting for git.