folke / lazy.nvim

đź’¤ A modern plugin manager for Neovim
https://lazy.folke.io/
Apache License 2.0
13.45k stars 322 forks source link

feature: add compile status to lazy.nvim or to lazyvim when using plugins that need to be compiled #977

Closed beastr45 closed 11 months ago

beastr45 commented 12 months ago

Did you check the docs?

Is your feature request related to a problem? Please describe.

When I was using the lazynvim configuration I had enabled rust language support. After being enabled I had gotten very high cpu usage from rustc and assumed that there was a recursion bug or a memory leak caused by rust lsp. I quickly killed the processes only to have the insight 30mins later that a rust plugin feature was compiling. Due to a lack of ui feedback from both lazyvim and lazy.nvim i was unaware of the cause of the issue causing me to think it is an issue with lazyvim itself and not the plugin. I wasnt shure wheter to put this issue on lazy. nvim github or lazyvim github as they are both related to this issue. I think that my problem is just an oversight by lazy devs and by me but it would definitely confuse a beginner or someone who isnt experienced with nvim plugin dev.

Describe the solution you'd like

I order to fix this issue I would recommend for lazy.nvim to send out a nvim messagesimilar to what it does when installing something or updating the config. the message should display that it is compiling a plugin when it is compiling a plugin along with the compiler being used. I would also reccomend a way to be able to see the compiler status logs when using any type of compiler from the lazy dashboard as the compiling procces isnt linked to a terminals output so we are unable to see the status or progress of compilation.

Describe alternatives you've considered

I have tried to find a way to hook the terminals output to running rustc procceses but I dont think that i will spend time trying to hack what is basically a bug with terminal commands. Also I finished compilation so i dont think i need to worry about it any more for my setup specifically.

Additional context

No response

folke commented 11 months ago

this has nothing to do with lazy./nvim or lazyvim. that's just your lsp