-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typst support #230
Comments
Since the Typst parser is actually written in Rust, it should be relatively straightforward to make this happen. It's relatively low priority at the moment though, so unless someone else decides to pick this up, I can't give you a time estimate. |
Would you be able to provide some guidance? I might find the time to submit a PR but don't really know where to start. Maybe there is some similar example ? |
You'll want to look at |
…ntent in span so quotes aren't escaped
…of an environment's span
… possessives or conjunctions
…ove dict parsing to fit better
…ntent in span so quotes aren't escaped
…tions inside function
…non-mut The parser trait's parse method took an &mut, but it wasn't used anywhere and was causing significant problems interacting with closures. If it is needed in the future, I would suggest creating a seperate mutable parse method.
…ctly handle optional components
Thanks for the great work on Typst support @grantlemons! Since this issue hasn't been closed, I'll use it. = This is a test for Harper
We have a #figure([here]) <labelled>.
We can reference the @labelled figure. Harper raises concern with the reference, which by looking at the parser is not supported yet. {
"resource": "/home/quachpas/test.typ",
"owner": "_generated_diagnostic_collection_name_#0",
"severity": 2,
"message": "Did you mean to spell “@labelled” this way?",
"source": "Harper",
"startLineNumber": 5,
"startColumn": 22,
"endLineNumber": 5,
"endColumn": 31
} I think, references should probably be altogether ignored. What do you think? |
Similar to #56, I would like to propose support for typst.
There is a pretty good working languageserver for it, in case that helps with implementation.
The text was updated successfully, but these errors were encountered: