benbrastmckie / .config

NeoVim configuration optimized for writing in LaTeX
332 stars 281 forks source link

nvim errors #134

Open ammukuttu opened 1 day ago

ammukuttu commented 1 day ago

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:

gitsigns: Ignoring invalid configuration field 'current_line_blame_formatter_opt
s'
gitsigns: Ignoring invalid configuration field 'yadm'
'signs.add.hl' is now deprecated, please define highlight 'GitSignsAdd' e.g:
  vim.api.nvim_set_hl(0, 'GitSignsAdd', { link = 'GitSignsAdd' })
'signs.add.linehl' is now deprecated, please define highlight 'GitSignsAddLn' e.
g:
  vim.api.nvim_set_hl(0, 'GitSignsAddLn', { link = 'GitSignsAddLn' })
'signs.add.numhl' is now deprecated, please define highlight 'GitSignsAddNr' e.g
:
  vim.api.nvim_set_hl(0, 'GitSignsAddNr', { link = 'GitSignsAddNr' })
'signs.change.hl' is now deprecated, please define highlight 'GitSignsChange' e.
g:
  vim.api.nvim_set_hl(0, 'GitSignsChange', { link = 'GitSignsChange' })
'signs.change.linehl' is now deprecated, please define highlight 'GitSignsChange
Ln' e.g:
  vim.api.nvim_set_hl(0, 'GitSignsChangeLn', { link = 'GitSignsChangeLn' })
'signs.change.numhl' is now deprecated, please define highlight 'GitSignsChangeN
r' e.g:
  vim.api.nvim_set_hl(0, 'GitSignsChangeNr', { link = 'GitSignsChangeNr' })
'signs.changedelete.hl' is now deprecated, please define highlight 'GitSignsChan
gedelete' e.g:
  vim.api.nvim_set_hl(0, 'GitSignsChangedelete', { link = 'GitSignsChange' })
'signs.changedelete.linehl' is now deprecated, please define highlight 'GitSigns

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

benbrastmckie commented 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.

benbrastmckie commented 1 day ago

If you find a solution, please post it here for others. And no worries if you can't. I'll get to this soon.