Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lsp4e-dev] Fwd: How to trigger lsp4e only when a specific condition is met?

Thanks Mickael

You are correct, I need to enhance the editor assistance according to execution/debug state.

I would definitely upload a video, once I make it work.

The referenced bug should solve my purpose as far as I understand.
For latest snapshot, should I re-install lsp4e using this link 
http://download.eclipse.org/lsp4e/snapshots/ ?

I remember using the snapshot version of lsp4e in my Devstudio, but it's been a while, I guess I need to update it.  

Thanks

Regards
Geetika Batra
                         ''~``
                        ( o o )
+------------------.oooO--(_)--Oooo.------------------+
|                                                     |
|                    .oooO                            |
|                    (   )   Oooo.                    |
+---------------------\ (----(   )--------------------+
                       \_)    ) /
                             (_/


On Thu, Dec 21, 2017 at 12:11 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
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


_______________________________________________
lsp4e-dev mailing list
lsp4e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/lsp4e-dev



Back to the top