Closed hhammoud01 closed 1 year ago
Maybe there is some problem with your nvim installation, I have never met this problem before. Try to uninstall your nvim completely (brew uninstall neovim
), and then reinstall nvim (brew install neovim
).
I do not think this is an issue of this config, maybe something wrong with everforest.
I have not seen this issue anywhere online.
I have followed the instructions carefully in the docs for the installation (dependencies + nvim + config / Packer plugins).
nvim --version
:Terminal: iTerm2 - Build 3.4.15
Operating system/version: MacOS Monterey - Version 12.2.1
Output of command
set runtimepath
:Describe the bug
Upon opening a python file, I get this error (occasionally and not with all python files). Unfortunately there is no deterministic way of reproducing it as it does not happen with all the py files that I have.
If it helps, the python file is part of a Flask project.
When I perform
checkhealth
normally (i.e, when I do not get the above error), it does not give any error and everything is checked with "OK".Only when I get the above error, if I press
return
, it continues to vim. Upon performingcheckhealth
in that case, I get this error:finally, it seems like an issue with color schemes particularly, but I am not sure, maybe with term colors.
I spent 2 days trying to search for a solution without any luck.
Lastly, the config is untouched. It is in sync with the latest branch of this nvim config.