option to delay starting lsp

[martinetd]

Hi,

apologize if this is already done, I didn't find how.
My problem is that rust-analyzer in particular is quite hungry, and I tend to have a dozen of terminals open with editors left running around left and right when looking around (especially for rust as I'm just dabbling and need to look up how things are done in other projects when I'm trying to fiddle with something...)

In this case, I don't need the LSP in code I'm not doing to edit.

For vim with ALE (the setup I'm switching from), there's let g:ale_lint_on_enter = 0 which will delay starting rust-analyzer until some edit is made, which I find is a good compromise. There also are case I'll want to run the lsp immediately but I find it acceptable to compromise there and make a noop edit to start it.

Is there a way of doing that I missed? Would that be possible?

Cheers!

[martinetd]

Bump (not sure if this actually works) a couple of years later -- I checked docs again and still don't see anything similar, perhaps it can be done with a plugin or something? but I didn't see anything about that either so far.

(I also saw helix should re-use an existing lsp if there was one for the current project? But I don't see how that'd work in stdio mode, I'm guessing that was a comment about multiple buffers in the same helix process, not multiple helix processes)

I guess I could setup an alias with a different config to not start the lsp when I'm just viewing ( cf. #10226 ) but I'd have to re-open the file if I change my mind after the file has been opened with editor.lsp.enable=false afaiu...

So, is any of the following possible as is?

• make it possible to only start lsp when first actively used (e.g. edit or request type info or something) ; yes that might take a while, it's fine.
• stop the lsp if the buffer was idle for more than x minutes/hours and restart on first activity (I couldn't get the lsp to restart after :lsp-stop, command like :lsp-restart didn't seem to work?)
  • it's not ideal if I start many helix at the same time, but my memory problem with rust-analyzer mostly stems from idle sessions, so I'd live with that and it might actually be the most ideal configuration from a comfort point of view in normal use
• have an option to not start the lsp at startup but have e.g. :lsp-restart enable it later; that could be bound to some easy to hit key and would be close enough to the first case for me.

Would any be easy enough to do, and merged if I open a PR? (I don't mind putting my feet in if that helps)

Thanks!