Sindre T. Strøm

Different than what?

The first image uses custom highlights. These are not the default highlights set from `diff.vim`:  > but it's more right than when these highlights were cleared and more wrong...

I don't know what mean by the highlights being "broken". There's nothing broken about these highlights. They are either set or not. You have brought my attention to the fact...

No worries, I didn't take it as such. Apologies if I came across as defensive. I was merely using concise language for the sake of clarity. Your issue did lead...

There's not such feature currently implemented, no. I'd be open to include it though, so if you are going to work on a solution for this, please consider opening a...

@TheodorRene Nvim has no issue opening big files. I can open a 100mb file instantly with: ``` nvim -u NORC --noplugin bigfile.txt ``` The culprit is almost certainly related to...

We could potentially allow passing the `--no-index` flag to `:DiffviewOpen` which would solve this: ``` git diff [] --no-index [--] This form is to compare the given two paths on...

The patch file idea is interesting. Feel free to open an issue about it so that we can track it separately.

We don't change any builtin highlights here. This is related to your color scheme. If you wish to customize the diff highlights, the relevant groups are documented under `:h hl-DiffAdd`.

Creating a buffer with a valid diffview URI will not automatically populate it with content. It will just be an empty buffer. We don't have `BufReadCmd` auto commands set up...