Documentation issue1529 issue1530

[JeremyBois]

Add documentation to Troubleshooting section to explain how to solve #1529 and #1530.

@moodmosaic @rwols

[rwols]

Yeah, looks good to me. @rchl or @predragnikolic any thoughts?

[predragnikolic]

Looking at this :)

[predragnikolic]

I'll be a critique on this one, but bare with me :)

I don't thing that the 4 point - Popup error Language server <your_server_language_name> has crashed is necessary, because it was described in the 2 point. Just moving it to a 4 point doesn't make a big difference. :)

Lets compare point 3 - Error in build streamingProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
with point 2 - LSP cannot find my language server (No such file or directory: 'xyz').
They both try to solve the same issue: does not exist (No such file or directory).

Point 3 is not a generic solution, it is tailored for the Haskell ecosystem,
while the point 2 has is more generic.

I am curious to see why the second step didn't help you to solve your problem in the first place? (Was it not clear, was it missing an example, what could we do to make the second step more)

Summary:
I think the current troubleshooting guide is simpler, than the one in this PR.

If you could just pin-point the problems you had and say that a particular paragraph/s wasn't clear in step 2.
The goal is to make the current troubleshooting guide more simpler :)

[JeremyBois]

I don't thing that the 4 point - Popup error Language server <your_server_language_name> has crashed is necessary, because it was described in the 2 point. Just moving it to a 4 point doesn't make a big difference. :)

Actually I did not get the message No such file or directory: "xyz" but only a message indicating the crash of the plugin. So I think a proper section can help a future user.

Also an alternative solution is added in the document. It consists of updating env variable directly in the LSP settings for a specific server. This approach allows to only expose a folder for a specific language server.

Lets compare point 3 - Error in build streamingProcess: runInteractiveProcess: exec: does not exist (No such file or directory) with point 2 - LSP cannot find my language server (No such file or directory: 'xyz'). They both try to solve the same issue: does not exist (No such file or directory).

Again yes, the same solution for another issue. In this case the problem is a missing dependency with a working language server. For instance when the binary for the language server and one of its dependency is not in the same folder.

Point 3 is not a generic solution, it is tailored for the Haskell ecosystem, while the point 2 has is more generic.

Yes I agree with this one. The error message is linked to Haskell in this case but the missing dependency is always specific to the server. Maybe I could remove this part and add a note on missing dependencies issue ?

If you could just pin-point the problems you had and say that a particular paragraph/s wasn't clear in step 2. The goal is to make the current troubleshooting guide more simpler :)

As said above, I never get No such file or directory: "xyz", so the current troubleshooting was not directly useful.

Summary:

• Point 4 is different from point 2 even if the solution is the same
• Point 3 is too specific and could be removed
• A note about a missing language server dependencies is needed
• Added alternative solution avoid polluting the global user space only for a specific server

[predragnikolic]

I would just suggest removing the 3rd point from the troubleshooting guide.
The rest what you said in your summary is ok.

[rchl]

I don't think this should be here. The reasons for server crashing can be plenty and I don't think a wrong PATH is a frequent reason for those. I'd probably add it in the Haskell section in https://github.com/sublimelsp/LSP/blob/st4000-exploration/docs/src/language_servers.md instead.

[rchl]

The The exact changes to make paragraph (including the code block) should be in the Updating the PATH used by LSP servers section. Just maybe add info that this is a Linux specific method.

[rwols]

We can only ask so much from contributors. Maybe we can merge this and then you can make the adjustments, @rchl?

[rchl]

We can only ask so much from contributors. Maybe we can merge this and then you can make the adjustments, @rchl?

I can do that when I find time and courage.