nvim-lua / lsp-status.nvim

Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
MIT License
621 stars 41 forks source link

Issue with Navic #87

Closed unphased closed 1 year ago

unphased commented 1 year ago

I used most of the snippets from the cookbook, in the order they were presented, and I probably have a too new version of navic I'm guessing? Need help debugging:

E5108: Error executing lua ...local/share/nvim/lazy/nvim-navic/lua/nvim-navic/init.lua:439: bad argument #3 to '__index' (string expected, got table)
stack traceback:
        [C]: in function '__index'
        ...local/share/nvim/lazy/nvim-navic/lua/nvim-navic/init.lua:439: in function 'condition'
        ...hare/nvim/lazy/heirline.nvim/lua/heirline/statusline.lua:284: in function '_eval'
        ...hare/nvim/lazy/heirline.nvim/lua/heirline/statusline.lua:365: in function '_eval'
        ...hare/nvim/lazy/heirline.nvim/lua/heirline/statusline.lua:365: in function '_eval'
        ...hare/nvim/lazy/heirline.nvim/lua/heirline/statusline.lua:365: in function '_eval'
        ...hare/nvim/lazy/heirline.nvim/lua/heirline/statusline.lua:440: in function 'eval'
        ...ocal/share/nvim/lazy/heirline.nvim/lua/heirline/init.lua:89: in function <...ocal/share/nvim/lazy/heirline.nvim/lua/heirline/init.lua:84>

Let me know if details are needed.

The other bit of info I have now is that simply not including the Navic bar component resolves the error so it's not caused by the navic code. I slightly suspect simply calling setup on navic before running heirline config might do the trick. Will test that now.

unphased commented 1 year ago

Not related but figured i would avoid making too many issues: I see ![▲ 1 ⚑ 13] for Diagnostics. Not sure why the ![] are appearing. Not sure what syntax this is. Just removing these chars from provider defs for now.

unphased commented 1 year ago

Crap. Posted this issue in the wrong repo!