catppuccin: different name

[neutaaaaan]

As originally discussed when we started porting preexisting colorschemes to vim, and as I believe is implied in this closed issue in the catppuccin repo, we ought to find a different name for our version of catppuccin, and we ought to settle on it fast before distros start rebasing upon 9.2.

An obvious candidate would be espresso, as all upstream variations of catppuccin are named after coffee.
On the other hand, I'm unaware of which of these variations "our" version is closest to, which may influence this choice.

[habamax]

Vim9.2 is already out, additionally, catppuccin maintainers gave us a go with using the name with what we bundle in vim, probably linked in the same issue catppuccin/vim#29 (comment)

[neutaaaaan]

While it is true that the authors gave us permission to use the same name, I believe this is misguided and will only create confusion.

I don't expect an end user to know or care about whether they're using catppuccin the built-in colorscheme, or the plugin.
I especially don't expect anyone using a vim distribution (of which there are many) to know which version they're using.
I do not expect someone copying their config over to a new version of vim to understand why their previously working catppuccin now looks weird.

This will do nothing but pollute the upstream repo with issues about our version.

[romainl]

I agree, using the catppuccin name is confusing. A different-but-related name would have been more appropriate, if only because this colorscheme is actually quite different from the one you would get from upstream. Confusion will happen.

But I think that there has been enough discussion about this, with the maintainers of Catppuccin and the author of this "port". And 9.2 already shipped anyway and it would probably not be super wise to change the name now.

Let's try to be more strict next time.

[neutaaaaan]

As I said in my initial post, 9.2 may have shipped, but it's still recent enough that we can hope and maybe even assume no distribution will rebase upon 9.2.000.

[mao-yining]

Catppuccin has two ports: one for Vim (Vimscript) and one for Neovim (Lua). Their performance differs mainly due to the differences between Vim and Neovim themselves.

The Vim port isn't very actively maintained, so it has fallen behind the Neovim port.

I submitted a PR to fix this: catppuccin/vim#30. But the maintainer seems too busy to review it right now. If that PR gets accepted, the Vim port would be identical to upstream. Still, users can continue using this repo to get support for various plugins like LSP, vim-dir, rainbow, etc.

Finally, the Neovim port has been renamed from catppuccin to catppuccin-nvim, which I think is the final solution.

So @habamax @neutaaaaan, I think this issue can be closed. Thanks.