Emeka Nkurumeh

when you say "Build On Save" do you mean an actual build or a format job being run? sublime text refers to both as a "Build".

which version of sublime text are you using? in previous versions of sublime text they were called `file_regex` and `line_regex`, but they were changed to `result_file_regex` and `result_line_regex`. in build...

if possible could you open the console run `sublime.log_result_regex(True)` and then manually perform a build (other than a format) and then paste the output from the console?

could you elaborate on what kinds of path errors you were getting? i don't there should be any real issues with `zig build` unless you are using some sort of...

i see no issue with 1 as often do the exact same thing, but i neglected is to test that while i was writing the extension.

i think i'm going to rework a lot of the syntax file to adhere to [this](https://www.sublimetext.com/docs/3/scope_naming.html) hopefully this doesn't break anything such as the linguist syntax highlighting.

i think this would require an upstream change on github's part to differentiate between `comment.*.documentation` scopes and `comment.*` scopes.

related: https://github.com/ziglang/zig/issues/615

[SublimeText/PackageDev](https://github.com/SublimeText/PackageDev) supports outputting a `.YAML-tmLanguage` as a json file that vscode can consume. perhaps [here](https://github.com/ziglang/vscode-zig/blob/813c83aed07c9037f5e6ec23843bfcb63f64fd47/package.json#L82) we could download the syntax file generated and kept in this repo and use that...

make sure you call `dyad_setNoDelay` on your stream to disable nagle's algorithm for your stream.