trouble.nvim
trouble.nvim copied to clipboard
folke
🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
Currently, using `:Trouble quickfix` with gives a worse developer experience than using the built-in quickfix window plus `:cnext`/`:cprevious`. The quickfix `:cnext`/`:cprevious` commands will jump to the correct line even if...
Hi, First of all, I really love trouble (pun intended?) and think it is an awesome plugin! I moved all my quickfix/loclist workflow to use trouble instead for some time...
when do cmd :Trouble 
Hi, this might be a very beginner-ish question. I am using Trouble together with https://github.com/folke/todo-comments.nvim and it would be amazing if it could display both types of errors (todo comments...
Using both tsserver and null-ls with prettier and eslint I only get diagnostic reports from open buffers instead of the entire project. I read in another issue that it seems...
There is a typo on line 164 of README.md 163: * lsp_definitions: definitions of the word ... 164: * lsp_type_definitions: ~~tupe~~ **type** definitions of ... 165: * quickfix: [quickfix](https://neovim.io/doc/user/quickfix.html) items
As virtual text is a bit constrained, I would like the ability to pick/choose which plugins actually display in my virtualetext area of neovim. I am not seeing a way...
By default it seems that trouble is continuously refreshing alerts and errors which can create an annoying editing experience. Is there some way to throttle a refresh of inline warnings...
