Jeremy Saklad

> Incidentally, delta development has come across some other areas where perhaps there's room for improvement in git. They both relate to `git diff`. Firstly it doesn't handle shell process...

Git has two broad types of commands: "porcelain" (for humans) and "plumbing" (for machines). Porcelain commands are almost exclusively wrappers around plumbing commands, and plumbing commands allow you to do...

> OK, but which application would compute the diff if not git? That's the thing: `git diff` is just a wrapper for the low-level commands, and it is outright encouraged...

The issue here is that Alacritty is using the native color space, not the P3 color space. For everything short of a reference display (latest MacBook Pro, Pro Display XDR,...

> clean git clone, checkout [b16fe12](https://github.com/alacritty/alacritty/commit/b16fe1259cebcd6adb4bc92f7025beb696412b89): separate git clone, checkout [f4bdf5f](https://github.com/alacritty/alacritty/commit/f4bdf5fb36fdf3b329be8253da39050abe7238a5) downloaded release 0.10.1 > > > > > > > > EDIT: double checked, all #FF9E64 EDIT: on checkouts,...

@kchibisov Is what I described, allowing color spaces to be specified along with each hex code, feasible given Alacritty's current architecture? I consider color accuracy non-negotiable in anything encouraging me...

Then at least pin it to a specific colorspace like everything else does.

And I think that if you use a digital color meter, Alacritty will be in the native color space and Vim will be in sRGB. Nothing about this is macOS-specific.

@sforli > This is just the shell no Vim, and yet not even the background color (#000000) looks the same. If there's one thing I *can* be certain of, it's...

Thank you for the detailed feedback, I really appreciate it!