Krish

I've encountered a similar problem before with Go https://github.com/alecthomas/chroma/issues/390, It appears that `Chroma` does not use semantics to highlight types. Fixing this is definitely a priority.

For a completely, invisible page break, a slimmed down version of your code did the trick: ```julia html""" let cell = currentScript.closest("pluto-cell"); cell.style.pageBreakAfter = "always"; """ ```

You can use the `-n` flag to prevent `cowsay` from mangling whitespace. ``` ❯ cowsay a | cowsay -n ______________________________ / ___ \ | < a > | | ---...

I'd like to add that `:reflow` should perhaps consider separators before newlines, as in languages where `\` is used as an escape sequence: ```python "Lorem ipsum dolor sit amet, consectetur...

+1 It's worth noting that `itm` has been transferred yet again: https://github.com/rtic-scope/itm

I think syntax highlighting based on filenames is frequent enough to be a valid consideration: | Language | Filenames | |-|-| | Shell | `.bash_aliases` `.bash_functions` `.bash_history` `.bash_logout` `.bash_profile` `.bashrc`...

Thank you @Leedehai for a well written out issue! However, the Typst team have already implemented this feature: >  - Source: https://typst.app/docs/reference/scripting/#modules

Thanks @Leedehai for clarifying there - I've just done a deep dive into import statements in Typst Here are a series of import statements and their equivalents in Python: |Python...

Surely the end user of Typst is responsible for the code that they chose to run? I don't see how this is much different from any other programming language, where...

There's a couple of similar requests which involve supporting some markup language inside of Typst (eg. #184) I don't think any of these will supported as a primitive in Typst,...