Closed mrjones2014 closed 1 year ago
I hit this a number of times, as well. Eventually it did begin responding again, so I didn't have to kill neovim. I don't have any more precise way to reproduce than you (and I'm not using the cache currently, since it doesn't support the legacy ft_highlights).
I wonder if this is something to do with writing to file...
What I propose is that I'll add some debugging to the colorscheme in the coming days and we can see where it hangs based on what's logged.
Another somewhat related issue is that if there is an error in the cached file, then a lot of the rest of the theme fails to load, e.g. you cannot regenerate the cache because the :OnedarkproCache
command doesn't get defined.
I think that bit should be basically wrapping the cache loading in pcall
That's a really great spot!
@mrjones2014 can you set log_level = "debug"
in your configuration? A onedarkpro.log
file should be generated in ~/.local/state/nvim/
Sure. I'll post back here if I notice the issue again.
Closing this after the new merge. Please re-open if you notice any performance issues.
Your OneDarkPro config
Error messages
none
Describe the bug
What I expect to happen
It compiles cache
What actually happens
Not very often, but every once in a while,
:OnedarkproCache
will hang Neovim and I have to kill it withkillall -KILL nvim
Reproduce the bug
I'm not sure any consistent way to reproduce, sorry. It happens maybe every 1 in 10-20 times if I had to estimate.
Run
:OnedarkproCache
a bunch of times until it reproduces.Final checks
minimal.lua
config file above and still get the issue:checkhealth treesitter