Open ammukuttu opened 1 day ago
Looks like gitsigns
has been updated and requires changes to be made to its config. I haven't updated my packages in a while (it's mid semester), so will look into this. Thanks for raising this issue. I'll see if I can get to it later today, but in case you don't want to wait, you can check out the gitsigns repo to see how to fix the breaking changes. You might also try cutting and pasting the error into ChatGPT and ask what to do in order to update the config. Shouldn't be too hard though can take some digging if you are not familiar with doing this sort of thing.
If you find a solution, please post it here for others. And no worries if you can't. I'll get to this soon.
Numerous errors in nvim. It started with seeing a funny character at the top tab where the filebuffers are open. After going through errors, nvim is able to function: ie build latex, check-in source.
I forked the .config folder and made no changes to contents. Tried removing neovim and reinstalling. It hasn't helped.
This is an extract of the error upon launch:
The main neovim windows has this error at the bottom:
There were issues reported with your **which-key** mappings. Use :checkhealth which-key to find out more
Running checkhealth as instructed shows several warnings