![]() Open Start Menu, type "environment" and select "Edit environment variables for your account". Refer to the following table on where this should be adjusted: Windows ![]() The solution is to make ST use the same PATH that is read by your shell (or OS in general in the case of Windows).Īdjusting PATH can differ based on the operating system and the default shell used. You can see what ST thinks your PATH is by opening the ST console by clicking on View > Show Console, and running import os os.environ in that console. Sublime Text might see a different PATH from what your shell environment uses and might not be able to find the server binary due to that. Consider sharing the output of this command in the report. ![]() If the server is crashing on startup, try running LSP: Troubleshoot server from the Command Palette and check the "Server output" for potential errors. If you believe the issue is with this package, please include the output from the Sublime console in your issue report! It might be a good idea to restart Sublime Text and reproduce the issue again, so that the logs are clean. Once enabled (no restart necessary), the communication log can be seen by running LSP: Toggle Log Panel from the Command Palette. Show verbose debug messages in the Sublime Text console. To get more visibility into the inner-workings of the LSP client and the server and be able to diagnose problems, open Preferences: LSP Settings from the Command Palette and set the following options: Option
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |