-
-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Couldn't find Zig Language Server (ZLS) executable at "/home/janne/.vscode-server/data/User/globalStorage/ziglang.vscode-zig/zls_install/zls" #1137
Comments
Something had a added this line:
into my VSCode user settings json file. I deleted that line and restarted VSCode and it works now. Maybe this got added when I started VSCode from within a WSL shell with |
Has a fix been found for this? I got this problem on WSL as well but deleting the line and reinstalling the Zig language extension failed to fix it. |
Until there's a real fix, I had to uninstall vscode, delete it's appdata folder, and reinstall. For windows: https://stackoverflow.com/questions/47689536/how-to-completely-uninstall-vs-code-on-windows Maybe you can get it working just by deleting some zls folder in |
this is an issue with the vscode-zig extension which is being tracked here. |
Zig Version
0.11.0-dev.1893+277015960
Zig Language Server Version
0.3.2
Steps to Reproduce
Start zig project with VScode by running
code .
in my zig project root.This used to work for several weeks, I suddenly started getting this today:
Directory
/home/janne/.vscode-server
doesn't exist. I wonder if zls is looking into the wrong directory somehow?I did use ZLS yesteray with Windows WSL, maybe VSCode WSL extension installation changed something that broke ZLS?
Expected Behavior
I'd expect ZLS to start without problems in VSCode.
Actual Behavior
Zig language extension in VSCode errors with:
Couldn't find Zig Language Server (ZLS) executable at "/home/janne/.vscode-server/data/User/globalStorage/ziglang.vscode-zig/zls_install/zls"
The text was updated successfully, but these errors were encountered: