Update terminal/editor defaults for zig tooling #60
Conversation
Solarized Dark keeps the contrast comfortable while matching other tools. Zig settings point the extension at the repo's toolchain and enable style warnings. Disabling git.confirmSync removes an extra modal in the daily SCM flow.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| //-------------------------------------------------- | ||
| // Zig Configuration | ||
| //-------------------------------------------------- | ||
| "zig.path": "${workspaceFolder}/bin/zig", | ||
| "zig.zls.warnStyle": true, | ||
| "git.confirmSync": false |
There was a problem hiding this comment.
The settings now force zig.path to ${workspaceFolder}/bin/zig. Because this dotfiles file is applied to every VS Code instance, the Zig extension will try to use that path even in projects that do not vendor a Zig binary and where Zig is expected to come from the user’s $PATH. In those projects the extension will fail to start, disabling linting and language features. Removing the override or pointing to a real installation path preserves Zig tooling while still allowing auto-detection.
Useful? React with 👍 / 👎.
Summary
Testing