neovide: Breaking changes and new issues on main

The main branch has been updated with big improvements to the rendering, but also have following breaking changes and new issues compared to the latest 0.11.2 release.

  • Neovim 0.9.2 is needed
  • All configuration file options and command line arguments are renamed to fit kebab-case, e.g. noidle is now no-idle
  • --no-fork has no effect on Windows, the process is always a Gui application without console output.
  • --vsync is now on by default and g:neovide_refresh_rate does not have any effect unless you set --no-vsync
  • --multigrid is the default and highly recommended. If you want to disable the animations you can set g:neovide_cursor_animation_length, g:neovide_scroll_animation_length and/or g:neovide_position_animation_length to 0.
  • The length of the g:neovide_scroll_animation length is not exact anymore and might differ slightly from the previous setting, so you might have to adjust it slightly, for more information see https://neovide.dev/configuration.html#scroll-animation-length
  • There’s a new setting g:neovide_far_scroll_lines , which controls how much scrolling there is when you make long jumps, for example to the beginning and end of the document. That animation is much shorter than the previous default, but setting it to 9999 emulates the old behaviour.

Note that the following issues are still open, if those bother you it’s recommended to set g:neovide_scroll_animation_length to 0. Or maybe find an alternative to using the winbar. For floating windows, switching the plugin might be an option, only native borders are an issue, so plugins using plenary or nui work correctly. (fix pending in https://github.com/neovide/neovide/pull/2165)

The following issue needs fixing on the Neovim side :set inccommand=split doe snot work

On macOS there are these issues

On Windows make sure you have recent Nvidia drivers 526.47 or newer for slightly reduced frame drops. It has the setting Vulkan/OpenGL present method/Prefer layered on DXGI Swapchain, either true or auto(default) is ok.

I hope I didn’t forget something important, but if I did, please let me know.

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 19 (16 by maintainers)

Most upvoted comments

I think this has served its purpose now, so closing and unpinning.

Ok ill do some more looking tomorrow.

Sure, I’ll try right now

@linrongbin16, yes that’s one of the issues mentioned in the original post:

Currently the only workaround is to either disable the smooth scrolling with g:neovide_scroll_animation_length=0 or find an alternative workflow to the winbar.

The issue is quite tricky to solve on the Neovide side, so we have this issue open in the Neovim repository:

But I don’t think it has a high priority for them, and I have since then got an idea of how to fix it on our side. So, I think I will start working on fixing it soon. BTW, floating windows with native neovim borders have the same issue, and a similar solution will be done for that case as well.

I’m not 100% sure that my idea of fixing it will work, but I think so. I will be using the highlight groups to detect certain elements (borders, winbar) that should stay in place, and then only scroll the inner areas.