fine-cmdline.nvim
trouble.nvim
fine-cmdline.nvim | trouble.nvim | |
---|---|---|
16 | 59 | |
407 | 4,748 | |
- | - | |
2.2 | 7.6 | |
about 2 months ago | 18 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.
fine-cmdline.nvim
-
Do You Use Neovim's TUI or a GUI Client?
I have fine-cmdline.nvim. It does what I need but it doesn't the UI I want. Is basically a floating input, nothing fancy.
-
cmdheight = 0 discussion in vim_dev
In your reply you mentioned that users can create plugins with "better" ui for cmdline and link to https://github.com/VonHeikemen/fine-cmdline.nvim
-
What are some of your favorite eye candy plugins?
fine-cmdline.nvim, enter ex-commands in a floating input (uses nui.nvim).
-
`set cmdheight=0` merged into Neovim master
Potentially https://github.com/VonHeikemen/fine-cmdline.nvim?
-
Is there a plugin that customizes the command line area? And is there any way to customize the tab without plugins? I enabled the tab natively with vim.o.showtabline = 2. thx
For the command line area there is fine-cmdline. Haven't used it personally.
-
Looking for Vscode-like command palette in neovim.
There isn't. Not a real pretty command palette anyway. There is fine-cmdline, but that just offers you a floating input.
-
Command line in floating window?
Although I remember I saw fine-cmdline, maybe that's what you're looking for (I haven't tried it myself)
-
moving statusline from above cmd row to below it at the actual bottom of the window
I've been using it for a few weeks and other than not being able to see the command line (which can be solved with another plugin), it's basically perfect.
-
dressing.nvim: customize your vim.ui in Neovim 0.6
In fine-cmdline I use an on_change event (provided by nui.nvim's input) to manipulate an internal variable in realtime. It's what's makes possible "smart history search".
-
if you use fine-cmdline, I have a question for you.
fine-cmdline.nvim is the plugin.
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?
cmp-cmdline - nvim-cmp source for vim's cmdline
impatient.nvim - Improve startup time for Neovim
dressing.nvim - Neovim plugin to improve the default vim.ui interfaces
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]
neovim - Vim-fork focused on extensibility and usability
AutoSave.nvim - ๐งถ Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
wilder.nvim - A more adventurous wildmenu
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
nvim-mapper - A neovim plugin that helps you keep track of your keymaps.
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
dash.nvim - ๐๐จ Search Dash.app from your Neovim fuzzy finder. Built with Rust ๐ฆ and Lua
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.