Veikka Tuominen
Veikka Tuominen
The first issue was fixed in https://github.com/ziglang/vscode-zig/commit/1b6dfd19550eed115117ee7c2fb6c4625db54fca and the second is tracked in #86.
Nobody actually confirmed if this was fixed so I don't know. Could you give details on your installation process and setup?
The only reasonable way it wouldn't get registered is the initial setup failing; do you have `zig.initialSetupDone` set in your global config?
I wasn't able to reproduce your issues by setting the settings readonly and changing the workspace settings should have the same effect as global settings. Are you getting a modal...
Can you try if 0.5.3 fixed this for you?
> I think the main problem is documentation. > > It's unclear from the docs or setup that these settings need to be set: They need to be set but...
By "0.5.3 branch" you mean the extension reports version 0.5.3? Can you try setting `zig.checkForUpdates` to `false`? It's the only other setting I can think of that it could be...
I don't want users to have to read documentation to use the basic funcionalities of the extension and I think the initial setup is now good enough to accomplish that....
Note that `zigup` is redundant with this extension installed.
Is you vscode config file read only? The extension should be setting `zig.initialSetupDone: true` after you have selected one of those options once (other than cancel).