fidget.nvim
trouble.nvim
fidget.nvim | trouble.nvim | |
---|---|---|
25 | 59 | |
1,766 | 4,777 | |
- | - | |
9.2 | 7.6 | |
about 1 month ago | 23 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.
fidget.nvim
-
Poor performance in tmux
Iโm experiencing the same but only when fidget.nvim is being displayed
-
fidget.nvim: rewritten and revived
Following a very long slump (and some questionable release management practices), I've finally gotten back into maintaining my own plugin, fidget.nvim, starting with a long-overdue rewrite.
- Neovim consuming 5gb of Ram after a day of being open on a tiny project
-
[Help needed] lsp logging in editor
j-hui/fidget.nvim, That is the plugin is causing that. :)
-
Does anyone have a `cmdheight=0` setup, without Noice.nvim, that they are happy with?
I have been happily using cmdheight=0 for a while now, without noice.nvim. My strategy was simply to add some extra components in the statusline (search result, macro recording, connected LSP servers) paired with fidget.nvim for LSP status updates.
-
Any way to get the fetching status of Copilot in lua line?
it's up to you how you want to hook these things up, maybe with winbar or statusline, or even a virtual text like in fidget.nvim
-
lua_ls hover action not showing any documentation
Not sure if its specific to you, I just found the lua lsp to be slow af. It takes ages to load the workspace. I use fidget nvim to watch for the workspace to load b4 I do anything.
-
nvim-lsp-notify plugin to notify about LSP progress
I have been using fidget.nvim for this purpose for quite a while.
-
How can I disable initial lsp errors
I finally found the culprit. j-hui/fidget.nvim not formatting the long output correctly.
-
sumneko lua double notifications / workspace loading/diagnosing concerns
I was buffled by this for a long time and I thought it was a problem in my config as well but I found out that it is normal behavior. I saw it explained in an issue in the sumneko Lua repo but I can't find it at the moment. You can use fidget.nvim for a less spammy lsp report.
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?
nvim-lspconfig - Quickstart configs for Nvim LSP
impatient.nvim - Improve startup time for Neovim
popup.nvim - [WIP] An implementation of the Popup API from vim in Neovim. Hope to upstream when complete
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]
lualine-lsp-progress - LSP Progress lualine componenet
AutoSave.nvim - ๐งถ Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
typescript-language-server - TypeScript & JavaScript Language Server
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
bad-apple.vim - Do you wanna watch "Bad Apple!!" on your vim/neovim?
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
lsp-status.nvim - Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.