[X] I am using the latest stable release of Neovim
[X] I am using the latest version of the plugin
Neovim Version
0.10.0
Neorg setup
N/A
Actual behavior
Neorg seems to break whenever otter integration is activated and one tries to edit a file with an alternate filetype.
Expected behavior
No error.
Steps to reproduce
Enter a .norg file
Activate otter integration
(optional) disable otter integration
Move to a separate file
Potentially conflicting plugins
No response
Other information
(cc @benlubas, you're likely to know what the root cause of this issue is much faster than I am :p)
Below is the error log. It doesn't point to any individual Neorg path, but the error only triggers once the otter integration itself is activated.
Error detected while processing DiagnosticChanged Autocommands for "*":
Error executing lua callback: ...rro/.local/share/nvim/rocks/rocks_rtp/lua/otter/init.lua:184: attempt to index a nil value
stack traceback:
...rro/.local/share/nvim/rocks/rocks_rtp/lua/otter/init.lua:184: in function <...rro/.local/share/nvim/rocks/rocks_rtp/lua/otter/init.lua:183>
[C]: in function 'nvim_exec_autocmds'
...0/nvim-linux64/share/nvim/runtime/lua/vim/diagnostic.lua:1033: in function 'set'
...im-linux64/share/nvim/runtime/lua/vim/lsp/diagnostic.lua:260: in function 'handle_diagnostics'
...im-linux64/share/nvim/runtime/lua/vim/lsp/diagnostic.lua:293: in function 'handler'
...0/nvim-linux64/share/nvim/runtime/lua/vim/lsp/client.lua:1005: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>
Prerequisites
Neovim Version
0.10.0
Neorg setup
N/A
Actual behavior
Neorg seems to break whenever otter integration is activated and one tries to edit a file with an alternate filetype.
Expected behavior
No error.
Steps to reproduce
.norg
filePotentially conflicting plugins
No response
Other information
(cc @benlubas, you're likely to know what the root cause of this issue is much faster than I am :p)
Below is the error log. It doesn't point to any individual Neorg path, but the error only triggers once the otter integration itself is activated.
Help
None
Implementation help
No response