You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TexLab it the LSP implementation for TeX/LaTeX, so some kind of integration and code sharing (not sure about this point, but you might know better) is probably possible.
The text was updated successfully, but these errors were encountered:
I'm not sure that's really feasible. I'm very slowly becoming familiar, but my impression is XeTeX doesn't work like a familiar code compiler. It doesn't have distinct parsing and IR/optimising stages; I think the engine reads a token and processes it immediately. (Or at least it only tokenizes and then executes token streams, not any higher level structure.) So if you wanted the reusability of e.g. the syn crate for Rust code, then no dice. If you wanted to know whether commands are defined or not and what arguments they accept, then not really no, that's a highly dynamic concept that changes from line to line. The engine does virtually no static analysis, so there is no static analysis we can carve out and make reusable. You can feel this is intuitively true because all the TeX errors you ever get are 'bailing out midway because this input does not make sense given what I've already processed', with debug dumps of varying degrees of effort trying to map the current engine state back to what you typed.
TexLab it the LSP implementation for TeX/LaTeX, so some kind of integration and code sharing (not sure about this point, but you might know better) is probably possible.
The text was updated successfully, but these errors were encountered: