telescope-ui-select.nvim
trouble.nvim
telescope-ui-select.nvim | trouble.nvim | |
---|---|---|
9 | 59 | |
675 | 4,748 | |
7.7% | - | |
5.7 | 7.6 | |
4 months ago | 13 days ago | |
Lua | Lua | |
MIT License | Apache License 2.0 |
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.
telescope-ui-select.nvim
-
Sorting code actions
For me something like telescope-ui-select.nvim solves that problem
-
Update for telescope-all-recent.nvim: Frequency Sorting now for dressing.nvim!
Frequency Sorting for vim.ui.select: Now you can enjoy (f)recency-based sorting for pickers started through vim.ui.select, provided by dressing.nvim or (untested) telescope-ui-select.nvim. For this to work, make sure to load telescope-all-recent.nvim AFTER dressing.nvim.
- How to use telescope to show code actions and codelens instead of noice?
-
better Telescope live grep UI?
You might have to install ui-select as well: https://github.com/nvim-telescope/telescope-ui-select.nvim
- How to enable numbers in a Telescope selection list?
-
Telescope UI-Select Configuration
Can anyone point me in the right direction to get telescope 'code actions' to look like the picture they list in their github? https://github.com/nvim-telescope/telescope-ui-select.nvim
-
Efficiently review past commits of specific file
See telescope-ui-select.nvim.
- [yaml-companion.nvim] Get, set and autodetect YAML schemas in your buffers
-
which session manager for nvim
neovim-session-manager * Automatically save and load sessions to/from a configurable directory based on cwd * Commands to load, save, and delete sessions use vim.ui.select(), so a telescope picker can be used if dressing.nvim or telescope-ui-select.nvim is also installed
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.
What are some alternatives?
dressing.nvim - Neovim plugin to improve the default vim.ui interfaces
impatient.nvim - Improve startup time for Neovim
neovim - Vim-fork focused on extensibility and usability
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]
harpoon
AutoSave.nvim - ๐งถ Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
session-lens - A session-switcher extension for rmagatti/auto-session using Telescope.nvim
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
neovim-session-manager - A simple wrapper around :mksession.
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
auto-session - A small automated session manager for Neovim
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.