trouble.nvim
telescope.nvim
Our great sponsors
trouble.nvim | telescope.nvim | |
---|---|---|
59 | 322 | |
4,722 | 13,961 | |
- | 5.7% | |
7.6 | 9.1 | |
7 days ago | 5 days ago | |
Lua | Lua | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
trouble.nvim
-
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.
telescope.nvim
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
for telescope.nvim (optional) live grep: ripgrep find files: fd
-
Neovim: creating keymaps in lua
Here we have a configuration for telescope.nvim, a very popular fuzzy finder.
- What is the reason people 'touch' a file before writing it?
-
What are the plugins/settings to be able to view individual file or folder contents while scrolling through files or folders?
EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim
-
What are some plugins that you can't live without?
Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)
-
Telescope.nvim: Fully Customizable Layout!
Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572
-
telescope-sg: a new way to do structural search in neovim
This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.
- Telescope.nvim: Find, Filter, Preview, Pick. All Lua, All the Time
-
Benchmarking some of my favourite neovim plugins over time
telescope.nvim
-
Why does vim.lsp.buf.definition open this window instead of taking me to the styles file (the same with tsserver and Volar)?
My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim
What are some alternatives?
impatient.nvim - Improve startup time for Neovim
fzf.vim - fzf :heart: vim
lsp-trouble.nvim - ๐ฆ A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing. [Moved to: https://github.com/folke/trouble.nvim]
fzf-lua - Improved fzf.vim written in lua
AutoSave.nvim - ๐งถ Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
telescope-fzf-native.nvim - FZF sorter for telescope written in c
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
Visual Studio Code - Visual Studio Code
lspsaga.nvim - improve neovim lsp experience
nvim-tree.lua - A file explorer tree for neovim written in lua