Dan Davison

I think that we should carry on thinking about how we can make this feature as good as possible. Maybe this question helps: what would your absolutely ideal way be...

cc @th1000s just in case you have any thoughts: the topic here is git's `--word-diff` output format, which merges sections of added and removed content together on a single line....

The current release (0.10.3) refuses to handle `--word-diff` or `--color-words` at all, instead allowing the raw git output through. I think this is at least a step in the right...

Hi @edi9999, to expand slightly on @Kr1ss-XD's answer: firstly, `delta file_A file_B` is a wrapper around `git diff --no-index` (since delta of course contains no diffing algorithm). But! As @Kr1ss-XD...

> If a tab is guaranteed to be the one character in a grapheme, then we don't need to process the graphemes individually: whatever comes before or after the tab...

Just stropping by to say that this branch will be great to have. Let me know when you feel that it's wrapped up.

Hi @lepotic, @tpoliaw you're right, I'm guilty here! I did deliberately set the help text to always be coloured. I did that because I wanted the colours to be present...

That would be great, and thanks for thinking about it. > Is less ubiquitous enough to assume that every *nix(ish) system has it? Yes, I think we can assume that...

> I also came here to either ask for a manpage or a help output that I can read in a pager like less. Hi @c0dev0id, that exists! It's `delta...

Thanks @ourigen! And sorry to be slow. I can reproduce this -- as you say, it looks like `hunk-header-style=raw` doesn't apply to the "frag" in the way one might expect...