Nathan Varner

@Jaggernaute are the logs you posted the complete logs? I'd expect more than just that. It looks like `typst-lsp` is aware of one of your documents, but I don't see...

I haven't yet made a release with this fix, but I expect to soon. I'll reopen the issue for now.

The new release, v0.10.0, is out now. @Andrew15-5 can you test again?

From the logs, it looks like VS Code isn't telling the language server about the unsaved file, so it can't highlight it. Do you know of another language that does...

@lyc-Lacewing are there any more LSP logs, particularly logs from when the language server was initializing? This is likely an encoding issue, and the encoding is decided at initialization.

The TextMate grammar in this repo is unused and unmaintained. We switched to semantic token highlighting because it's based on the Typst parser, so we don't need to keep up...

That was my original intention, but VS Code seems to make this hard. Semantic tokens are enabled/disabled as part of the LSP, so can be toggled controlled by configuration. However,...

Whatever you prefer is fine. I probably won't merge it until it's fully polished. (I would also accept one finished piece of a large project, but this is probably too...

Unfortunately, Typst is compiled into the language server binary, which means it's not possible to change the Typst version without an update. This means we can use internal Typst functionality...

It should be associated by default. What version of the extension are you using?