You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated navbuddy, and it errored out my neovim due to this change: 06525d0
That update totally makes sense to target the latest Neovim API, but if users are on an old version it might be tricky to figure out why it's broken.
I had an idea that it might be useful to add a version check like the following:
if not (nvim_version.major == 0 and nvim_version.minor >= 10) then
vim.api.nvim_err_writeln("WARNING: nvim-navbuddy requires Neovim v0.10.0 or higher.")
end
I think it's good to continue to run the plugin even if it's on an unsupported neovim, because it will still throw a loud message if it encounters an error.
This check may also be annoying since you would need to manually keep it up to date. But, at least it gives the user some extra information about why something might be failing, and what version the plugin is tested against. Feel free to use it or not, just an idea I'm toying with.
Thanks!
The text was updated successfully, but these errors were encountered:
Yo! Thank you for making this ❤️
I recently updated navbuddy, and it errored out my neovim due to this change:
06525d0
That update totally makes sense to target the latest Neovim API, but if users are on an old version it might be tricky to figure out why it's broken.
I had an idea that it might be useful to add a version check like the following:
I think it's good to continue to run the plugin even if it's on an unsupported neovim, because it will still throw a loud message if it encounters an error.
This check may also be annoying since you would need to manually keep it up to date. But, at least it gives the user some extra information about why something might be failing, and what version the plugin is tested against. Feel free to use it or not, just an idea I'm toying with.
Thanks!
The text was updated successfully, but these errors were encountered: