Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Otter integration breaks on alternate filetypes #1488

Open
2 tasks done
vhyrro opened this issue Jun 26, 2024 · 2 comments
Open
2 tasks done

Otter integration breaks on alternate filetypes #1488

vhyrro opened this issue Jun 26, 2024 · 2 comments
Labels
bug Issues related to bugs. Please attach a severity, a priority and category with this label.

Comments

@vhyrro
Copy link
Member

vhyrro commented Jun 26, 2024

Prerequisites

  • I am using the latest stable release of Neovim
  • 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>

Help

None

Implementation help

No response

@vhyrro vhyrro added the bug Issues related to bugs. Please attach a severity, a priority and category with this label. label Jun 26, 2024
@benlubas
Copy link
Contributor

I'm having trouble with otter not even updating diagnostics anymore. I'll add this to the list of things to look into

@benlubas
Copy link
Contributor

Can confirm that this also breaks with markdown files and is most likely a bug in otter.nvim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues related to bugs. Please attach a severity, a priority and category with this label.
Projects
None yet
Development

No branches or pull requests

2 participants