Re: [lsp4e-dev] Fwd: How to trigger lsp4e only when a specific condition

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi Geetika,

That's one unexpected and interesting use case! Do I get it right that you're trying to enhance editor assistance (completion, diagnostics...) according to execution/debug state? If so, first, I'd like to mention that I believe it's beyond the initial scope of LSP and that you may face some issues; and second that I don't see any reason why not doing it and I think you're basically bringing the LSP into a new set of use-cases I don't think anyone has tried yet. So thanks for trying, good luck and please share a demo whenever you can!

Now, for the specific question: it seems to relate to https://bugs.eclipse.org/bugs/show_bug.cgi?id=527329 .

First question is do you use the latest snapshot/commit? There are chances it fixes it magically.

If not, one thing to try is to make "start ()" send an exception when the LS shouldn't start, instead of calling stop (). With this, you may get into the soft error handling implemented in https://bugs.eclipse.org/bugs/show_bug.cgi?id=527329 .

HTH, and please keep us in touch.

 

--

Mickael Istria

Eclipse IDE developer, at Red Hat Developers community

Elected Committer Representative at the Eclipse Foundation board of directors