Techatrix

There isn't enough information in this issue to identify the cause. I have some questions that could be helpful to figure out what is going on: - What version of...

Could you clarify what you have set in your `zls.json` and VS Code `settings.json`? These 'simplified' logs are really confusing me...

The formatting issue should have been fixed by #233. The rest of the issue may be fixed by #252. Could you check whether that resolves your issue? Feel free to...

> 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. This issue should be fixed by fd95050f0a7f3f4c1ff628796760b9e4a055b8fe...

Could you elaborate on whether the logs you have posted are indicating that the LSP is setup as expected or not. I am a bit confused about how there is...

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.

> it was just neater using the .json file when ensuring server functionality with multiple editors. True, that is a nice advantage when using multiple editors. But besides that, based...

As may be evident from the mentioned workaround, the config option that the extension attempts to modify is `zig.zls.enabled`. I don’t think saving this in the global/user settings is a...

> The more intuitive behavior to me would be if the extension checks to see if the system-wide `settings.json` is read-only and fails over to saving it in the workspace...

### Select only the closest `build.zig` The problem with selecting the closest `build.zig` is that it can cause the reverse problem to occur. What if you root `build.zig` has a...