Matt McKay

thanks @JensHeinrich for looking into this. Would you like to submit a PR? Otherwise I can update the `render_outputs.py` file for the LaTeX builder tomorrow and I can add it...

wonderful - thanks @JensHeinrich (didn't see it there) I have `approved` the tests to run for the PR.

We have just released `myst-nb=0.13` -- that might be worth a try in a new environment to see if you still get the same issue. This release includes the latest...

- [x] check if this PR fixes https://github.com/QuantEcon/lecture-python.myst/issues/95 - [x] fix fixtures (the `unknown mimtype` fixture is removed as that test is current commented out in test_render_outputs.py)

> I don't think latex should be above svg hey @chrisjsewell can you explain why? (i.e. page load times?) `mathjax` seems to do a nicer job of displaying the math....

> Because svg is natively supported by HTML, latex is not roger that.

@chrisjsewell I see `epub` is listed as a `builder` in the builder option list. Do you know if `epub` has a mechanism to support `text/latex` like `mathjax` for `html`? Hmm...

One issue with the proposal of adding `:file:` as an option (rather than an argument) is that it becomes harder to support the usual `options` associated with, for example selecting...

Yeah -- not sure how to fully solve the "notebook source file" issue. One possibility is to keep that in tact (which I think is **very important** to keep two...

Another alternative would be to enable `myst_parser` to interpret `code-cell` with a file reference (or introduce `code-file` directive) and read the contents of the file directly on parsing.