But this is all acceptable for a reasonable Lua API. I know Bram's reasoning behind doing vim9script was that the mailing list preferred it, but my guess is that's not exactly representative.
Either way it would increase compatibility, which is good for everyone.
Maybe that'd be a viable approach for you?
Also, Neovide is a neat GPU rendered frontend. Maybe it has a bit of the color saturation effect you mention. I like to use it every so often when I want to see buttery smooth text and fancy animations.
Also, Neovide is a neat GPU rendered frontend. Maybe it has a bit of the color saturation effect you mention. I like to use it every so often when I want to see buttery smooth text and fancy animations.
If by that you want Vim to become compatible with Neovim Lua plugins, Vim will have to add and maintain compatibility with the whole Neovim non-Lua API as well (new functions, options etc). This will never happen.
I did go pretty deep into trying to save sessions, but they're basically all supposed to be used before quitting, which I never do, and the hooks for saving aren't really sufficient. It sucks because I usually have like 10 tabs, each with lots of splits and at least 1 terminal, and I lose it all every time.
