Troubleshooting
-
Should Neovide happen not to start at all, check the following:
-
Shell startup files if they output anything during startup, like
neofetch
orecho
. Neovide uses your shell to findnvim
and can't know the difference bewteen output andnvim
'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
Actions
tab on GitHub.
-
-
Neovide requires that a font be set in
init.vim
otherwise errors might be encountered. This can be fixed by addingset guifont=Your\ Font\ Name:h15
in init.vim file. Reference issue #527. -
If you installed
neovim
via Apple Silicon (M1)-basedbrew
, you have to add thebrew prefix
to$PATH
to runNeovide.app
in GUI. Please see the homebrew documentation. Reference issue #1242
Linux
-
If you receive errors complaining about DRI3 settings, please reference issue #44.
-
If your scrolling is suttering
-
Add flag
--novsync
before startup as a quickfix. -
Check if the value of
g:neovide_refresh_rate
and the refresh rate of your monitor are matched. -
If your
g:neovide_refresh_rate
is correct, then check if you are using dual monitors with mixed refresh rate, say144
and60
, by checking output ofxrandr
(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 setg:neovide_refresh_rate
to the lower value.
-