SaaSHub helps you find the best software and product alternatives Learn more →
Trouble.nvim Alternatives
Similar projects and alternatives to trouble.nvim
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
null-ls.nvim
Discontinued Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
-
which-key.nvim
💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
-
lspsaga.nvim
Discontinued improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim] (by glepnir)
-
symbols-outline.nvim
Discontinued A tree like view for symbols in Neovim using the Language Server Protocol. Supports all your favourite languages.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
trouble.nvim reviews and mentions
-
How to copy LSP diagnostics from folke/trouble to quickfix window?
Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?
-
Help with trouble.nvim
A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?
-
How can i get better looking errors?
Trouble
-
How do I get neovim to only show LSP errors as underline squiggles and not in the gutter?
Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.
-
Neovim vs VSCode Neovim - what are the tradeoffs?
All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.
-
Is it possible to close todo-comment/trouble's floating window after pressing enter on an item?
I am referring this as well as this this plugin.
-
Video: 5 Neovim Plugins To Improve Your Productivity
Trouble: https://github.com/folke/trouble.nvim
-
People who migrated from vscode
Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?
-
Any recommended plugins to frictionlessly see lsp references in a perhaps a popup window?
I like trouble.nvim
-
Disabling PEP diagnostics errors/warnings in LazyVim
I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.
-
A note from our sponsor - SaaSHub
www.saashub.com | 10 May 2024
Stats
folke/trouble.nvim is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of trouble.nvim is Lua.
Popular Comparisons
- trouble.nvim VS impatient.nvim
- trouble.nvim VS lsp-trouble.nvim
- trouble.nvim VS AutoSave.nvim
- trouble.nvim VS telescope.nvim
- trouble.nvim VS lspsaga.nvim
- trouble.nvim VS null-ls.nvim
- trouble.nvim VS lspsaga.nvim
- trouble.nvim VS vim-local-history
- trouble.nvim VS nvim-notify
- trouble.nvim VS nvim-treesitter-refactor
Sponsored