Should Neovide happen not to start at all, check the following:
Shell startup files if they output anything during startup, like
echo. Neovide uses your shell to find
nvimand can't know the difference bewteen output and
nvim's path. You can use your resource file (in the case of zsh
~/.zshrc) instead for such commands.
Whether or not you can reproduce this by running from the latest git main commit. This can be done by running from source or just grabbing the binary from the
Actionstab on GitHub.
Neovide requires that a font be set in
init.vimotherwise errors might be encountered. This can be fixed by adding
set guifont=Your\ Font\ Name:h15in init.vim file. Reference issue #527.
If you installed
neovimvia Apple Silicon (M1)-based
brew, you have to add the
Neovide.appin GUI. Please see the homebrew documentation. Reference issue #1242
If you receive errors complaining about DRI3 settings, please reference issue #44.
If your scrolling is suttering
--novsyncbefore startup as a quickfix.
Check if the value of
g:neovide_refresh_rateand the refresh rate of your monitor are matched.
g:neovide_refresh_rateis correct, then check if you are using dual monitors with mixed refresh rate, say
60, by checking output of
xrandr(wayland should support mixed refresh rate out of the box), if so,that's because X11 does not support mixed refresh rate well. You may be able to fix this through your compositor or by switching to wayland. As a temporary work around, you may set
g:neovide_refresh_rateto the lower value.