Comments (5)
A couple of days ago, I apparently switched up the "document" with "workspace" diagnostics, so lsp_workspace_diagnostics
actually showed those for the document only and vice versa.
This should now be fixed. Sorry about that
from trouble.nvim.
can we reopen this? I am getting the same behavior as well. It is only showing diagnostics from files open in buffers and not the workspace. or perhaps I am misunderstanding how workspace works? any help will be appreciated. Thanks!
from trouble.nvim.
Thanks, it's working now.
from trouble.nvim.
I'm running into this same issue. I also have nvim-lua/lsp_extensions.nvim
installed. I'm setting the callback as follows:
vim.lsp.handlers["textDocument/publishDiagnostics"] =
vim.lsp.with(
require("lsp_extensions.workspace.diagnostic").handler,
{
underline = false,
signs = true,
}
)
Calling :LspTroubleToggle lsp_workspace_diagnostics
still only shows diagnostics for the current buffer :/
Any advice would be greatly appreciated! Thank you!
from trouble.nvim.
@rphuber which language server? With Pyright, which I use most, workspace diagnostics are working. Perhaps it's simply not supported by your LS.
from trouble.nvim.
Related Issues (20)
- bug: The list background is displaying without color HOT 1
- feature: allow user to set winid HOT 1
- feature: Show spelling errors
- feature: better zen-mode.nvim integration
- feature: Enhanced Identification of `trouble.nvim` Mode
- Unable to view python output with "Trouble quickfix" HOT 12
- feature: order inline diagnostics by severity HOT 1
- bug: `Trouble lsp_definitions` do not work with the `pbkit` language server while `vim.lsp.buf.definition` does. HOT 2
- bug: column value outside of range HOT 1
- feature: events for opening, closing, and resizing Trouble window?
- feature: Remembering Current Entry State After Toggling Trouble Window HOT 11
- bug: `use_diagnostic_signs = true` no longer works due to a recent Neovim change (0.10+) HOT 4
- bug: typo / missing char in Readme HOT 1
- bug: is lsp-colors still needed? HOT 1
- bug: closing trouble after using a trouble command in netrw breaks trouble HOT 1
- bug: Neovim crashes when you close all other windows HOT 1
- bug: `:Trouble workspace_diagnostics` is only showing diagnostics for open buffers with tsserver HOT 1
- bug: list not properly formatted with the theme HOT 1
- bug: fatal error when `nvim-web-devicons` is installed but an icon is unavailable for the current file HOT 1
- Issue returning to previous view after jumping to an item in Trouble list HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trouble.nvim.