llogick

Try providing the full path to zig, including the executable, ie `C:\Program Files (x86)\zig\zig_0.10.1\zig.exe`.

I'm not confident enough in my Rust skills to PR it https://github.com/zed-industries/zed/commit/d40fb6a54168832bb71768302a26f0d41f9f6736

Hi, Just ran into a **similar** issue on a linux machine after a system update, although the view wasn't completely blank - the outline of the 'Welcome` tab was visible....

@WillLillis > I played with it a bit and noticed that in some cases the indention was inconsistent, e.g. I admit that I was aware of the indentation issue, but...

Upstream issue - https://github.com/zigtools/zls/issues/397

I've encountered this issue consistently. It's frustrating to constantly need to troubleshoot why settings aren't taking effect, only to discover that they're being overridden by the extension. Pay attention to...

0.6.5: ``` [Info - 9:26:08 AM] Starting ZLS 0.14.0-dev.407+b9c9b5ab @ '/home/rad/lab/z/zigscient/dev/zig-out/bin/zigscient' [Info - 9:26:08 AM] Log File: /home/rad/.cache/zls/zls.log (debug) [Info - 9:26:08 AM] Client Info: VSCodium-1.97.0 [Info - 9:26:08 AM]...

> Both the ZLS and the vscode extension itself want access to a zig executable. ZLS can be provided a zig executable through the zls.json but the extension has no...

> Would it no suffice to move the `zig_exe_path` setting from the zls.json to the settings.json? The latter also allows you to comment out the unused versions. Yes, I've arrived...

Initial support in https://github.com/zigtools/zls/tree/nullptrdevs/c012, > Excludes fields/switch cases that precede the current source_index, ie > ```zig > S{ > .a = 1, > .b = 2, > . // ^---...