Neovim v0.9.5 Released
github.com
Neovim v0.9.5 Released
1–10 of 11 posts
Re: Neovim v0.9.5 Released
#2I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had).
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.
Re: Neovim v0.9.5 Released
#3I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
100% with you, I use vim for exactly the same reason. With all due respect to Bram, and acknowledging that the project wouldn't exist without him, losing vim9scipt's designer immediately after merging it is a worst case scenario that shows exactly why it was a bad idea.
Re: Neovim v0.9.5 Released
#4I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
I had a ton of problems with Neovim GUIs too, so I went a different route: https://www.cweagans.net/2023/09/application-specific-termin...
Maybe that'd be a viable approach for you?
Re: Neovim v0.9.5 Released
#5I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
Are you using >=0.9? I havn't experience any stability issues and I use it at my full time developer job
Re: Neovim v0.9.5 Released
#6I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
Are you using >=0.9? I havn't experience any stability issues and I use it at my full time developer job
I've been using since 0.5, but full time since 0.7. Mostly this happens with long-running terminal jobs, but sometimes just randomly. There are definitely segfaults in there.
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.
Re: Neovim v0.9.5 Released
#7How does Neovim do release numbering?
Re: Neovim v0.9.5 Released
#8I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
I've never seen a neovim crash in my 5 years of using it with a riced up config (built on AstroNvim config)
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.
Re: Neovim v0.9.5 Released
#9I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
I've never seen a neovim crash in my 5 years of using it with a riced up config (built on AstroNvim config)
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.
Re: Neovim v0.9.5 Released
#10I really wish Vim would add Neovim's Lua API. GUI clients for Neovim all have subtle issues (color saturation, font rendering) and Neovim generally has stability issues (I've lost count of the number of crashes I've had). 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…
> I really wish Vim would add Neovim's Lua API
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.