crates.nvim VS fidget.nvim

rust-tools.nvim and crates.nvim should be helpful for you. :)

FYI: The versions come from the Saecki/crates.nvim plugin.

Hello! I'm trying to break up my existing init.lua file into multiple files according to the existing vim rtp. For example, I'm a rust developer and the crates plugin is extremely helpful for me but it's only ever useful when I'm editing Cargo.toml files. As a result I've put the plugin in pack/plugins/opt/ and I packadd crates.nvim in my init.lua file. This actually works nicely but when I try to factor the config and loading of this plugin into ftplugin/toml.lua it doesn't load despite it indicating that the file was sourced in the output of --startuptime. Curiously if I initialize the plugin in init.lua and then modify the config in ftplugin/toml.lua the updated config is used. So it seems like toml.lua can modify an already loaded plugin but can't load one itself. Is this the case? I'd very much like to relegate all toml related configs to its ftplugin file.

github.com/Saecki/crates.nvim

crates.nvim maybe?

So to fix the shortcomings I felt with vim-crates and to teach myself a bit of lua I created crates.nvim. It sports a nvim-cmp completion source, a popup that list all versions for a crate, live updates while editing and some more stuff that I found to be useful.

I’m experiencing the same but only when fidget.nvim is being displayed

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.

j-hui/fidget.nvim, That is the plugin is causing that. :)

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.

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

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.

I have been using fidget.nvim for this purpose for quite a while.

I finally found the culprit. j-hui/fidget.nvim not formatting the long output correctly.

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.