KillTheMule
KillTheMule
This very much feels like it should not be implemented explicitely by typst-lsp, but be exposed by typst itself, so that there's no chance of a discrepancy between what fonts...
I'm running ```lua root_dir = function(fname) return util.path.dirname(fname) end, ``` in my lsp config. I'm not clear what the right config here would be, although I think `typst-lsp` barely uses...
Can you post your config? disabling `exportPdf` works for me.
Yeah looks fine. I also checked again that it works for me :) Maybe you're still not using the right binary, but I know nothing of mason...
> Do you use VS Code? Did this issue exist for you in previous versions? No I'm using neovim. Issue existed before #281 for me, too.
Might mason somehow call a different binary though? Maybe try without mason? Shouldn't be too hard to just start a new config for testing.
Current HEAD (46e1b0b8a667c3d4c29bdd6388df83e12e5c02dd). If you checked the version with `typst-lsp -V` you woulndn't see the commit, right? So I'm still wary of mason ;)
> After restarting the Neovim: > >  Wait a second, how did that happen? My compiled typst-lsp does not do that, it just shows `Version: 0.9.5 (Typst version 0.7.0)`
Ah right, I missed that last commit ;) Still doesn't show a commit hash, though.
Ah I missed that part. I just used the included binary, and also with that, there's no pdf produced, neither when typing nor when savin the `typ` file.