Techatrix

@andrewrk Welcome to ZLS, happy to have you back! 🎉 We have missed you here since your last visit in 2020

> Why would installartifact matter for zls to identify imported module ? Declaring a compile step with `b.addExecutable` on its own has no side-effects. Every step needs to be reachable...

fixed by #2084

@paperdave Is the issue you have talked about?

I don't think there is much reason to implement this feature since your entire document should just be formatted based on `zig fmt`. What is the use case?

> It makes sense since formatting the whole buffer still uses the `textDocument/rangeFormatting` and not `textDocument/formatting`. Could you show me how you performed formatting and checked that it used `textDocument/rangeFormatting`?...

Could you try to compile ZLS with the following patch and then post the content of `/root/code/zls/langref.html.in`? A diff to https://github.com/ziglang/zig/blob/master/doc/langref.html.in would also suffice ```patch diff --git a/src/config_gen/config_gen.zig b/src/config_gen/config_gen.zig index...

no response...

Above Terminal is NeoVim 0.10.0, Bottom Terminal is Neovim 0.9.5 ## With ZLS  ## Without ZLS  In case this is hard to see, the escape characters are highlighted...

Perhaps it is more reasonable to assume that the editor already provides syntax based highlighting for Zig code? Then we could make `partial` the default which also fixes this issue.