-
Notifications
You must be signed in to change notification settings - Fork 177
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
bug: Cannot use trouble due to lua error #465
Comments
Trouble v3 was merged in main. Please check the docs. |
Sorry for necroing this issue, but I'm getting the same error on LazyVim 12.x with default lualine and trouble configs. Does this mean I just should not use the latest of the main branches? |
Trouble v3 has been merged in main ages ago. |
I am on the latest of all plugins. This my lazy-lock.json:
and lazyvim.json
I don't think anything is too old... |
ok, I thought this was something else. |
@antolu I use this: local trouble = require("trouble")
vim.keymap.set("n", "<leader>ed", "<cmd>Trouble diagnostics toggle<CR>", { desc = "document diagnostics on opened buffers" })
vim.keymap.set("n", "gr", "<cmd>Trouble lsp_references toggle<CR>", { desc = "go to references" }) |
That works fine for me? Op's problem was because they used a non-existing source. |
Cheers guys. Realized now I have a slightly different error for the status line, not the toggle. In case @folke is interested, it happens on launch of
From LazyVim/lua/lazyvim/plugins/ui.lua Sorry guys for hijacking this thread with an unrelated issue. |
Please open an issue in the LazyVim repo with a repro that triggers this. |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.10.0-dev-2752+g35239e977
Operating system/version
Windows 10
Describe the bug
Cannot use trouble due to lua error, using latest trouble version, I had no issues with this until yesterday, maybe because of a version update
Steps To Reproduce
require("trouble").toggle("document_diagnostics")
require("trouble").toggle("workspace_diagnostics")
Expected Behavior
It's supposed to not error and show diagnostics for the current file or workspace
Repro
No response
The text was updated successfully, but these errors were encountered: