-
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: Trouble shows no diagnostics results for scratch buffers #514
Comments
This is not a bug. If you need to show diagnostic for the buffer where the cursor is, try require("trouble").toggle({ mode = "diagnostics", filter = { buf = vim.fn.bufnr() } }) |
How is it not 0, if everywhere in nvim's API, a buffer ID of 0 means the current buffer? It works that way with telescope ( |
My mistake. trouble.nvim/lua/trouble/filter.lua Lines 34 to 39 in 2d8610a
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
@b0ae989c can you please remove the stale label? I don't think I'm allowed to do that. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.11.0-dev
Operating system/version
Ubuntu 22.04, WSL2, Windows 11
Describe the bug
When I toggle trouble for a scratch buffer, I get the following notification:
Steps To Reproduce
buf = 0
Expected Behavior
Trouble should list the diagnostics for the scratch buffer, just like Telescope is able to.
Repro
The text was updated successfully, but these errors were encountered: