Olle Lögdahl

I think this is out of scope by default, although a custom function should be able to parse the format. ```typst #let wavedrom(file) = { let text = read(file); ......

I created a small example how this could be implemented. It's not pretty or complete, but it might help you along: [test.txt](https://github.com/typst/typst/files/11051067/test.txt)

> @laurmaedje @ollelogdahl > > My idea is that don't need typst to parse code, just pass code to [wavedrom-cli](https://github.com/wavedrom/cli) to get the generated svg image, and insert it into...

I see reasonable use in personal projects ran locally (perhaps, sharing `paper.typ` for all research-papers in different directories), but I can see your point. While I deem `//` as a...

Another way to do it could be command-line arguments, kind of like how `cc` does include-paths. This would also allow multiple directories to look in. `typst -I /home/foo -I ~/macros`

> In many ways, this goes against the design philosophy of typst. Incremental compilation, that enables the expedient compilation we experience in the app, is due to the fact that...

> Maybe the `load` function [here](https://github.com/tloen/llama-int8/blob/main/example.py) will be useful? Thank you. Exactly what i was looking for!

I can take a look at this once #110 is completely solved.

@chrislusf great to hear. Suprised this hasn't been commented on earlier. I'm thinking a first pass would be Write/Read, but I guess in the long run more API:s could be...