Axel Rauschmayer

@bradzacher Right! That reminds me of the workaround that I used when I implemented similar functionality via the tsc API: I replaced each `@ts-expect-error` in the code with `%ts-expect-error` and...

FWIW: Given how flexible Djot’s syntax already is, it may not be necessary to introduce new syntax – e.g.: ``` [Figure](#fig:diagram){!float} visualizes how everything is connected. {!float for="Figure" #fig:diagram} :::...

I’ll update this code once there is an actual standard. At the moment, everything is in flux.

Can you explain what is going on? Interesting that one needs the hat (^), twice. That looks like a Node.js bug, you might want to report it (e.g. by posting...

I don’t know! openurl does very little, so it’s almost certainly a Firefox bug.

I’m regularly seeing screenshots of text on Mastodon, with plain text descriptions. In a way, the image it useless information in this case.

Ah, I should have checked other browsers: * This is only an issue in Safari (Mac with M1 Pro processor) – where I can type faster than my input is...

> Could you tell more about the intended semantics of `!cmd` syntax? * By default, parsers would simply ignore commands. They are mainly intended as extension points for Pandoc-style filters....

> It was probably a mistake to rely on the attribute comment syntax for comments; as noted above, I think a proper line comment syntax like LaTeX's `%` would be...

Couldn’t this be handled like CommonMark handles ``? * Inline comment: `