Maciej Katafiasz

31.12 Evalhook has ``, but references are to #evalhook-section

Not inside typst, that is actually a string. Try this: ```typst #let date = yaml.decode("date: 2024-07-01").date #type(date) ``` I don't believe YAML supports timestamps as much as it allows applications...

> I was wrong, it works for toml, not yaml, so you can define function > > ```typst > #let parse(s) = toml.decode("date = " + s).date > ``` That's...

@Coekjan: thanks for taking a crack at it! I'd say ISO 8601 should definitely be a supported (and likely default) format. Auto-discovery would be nice, but from what I understand,...

@Enivex: #1658 is what led to #1668, which got closed as insufficiently general (rightly so, IMHO). However, being able to ingest unix timestamps *as one of the options* would be...

Any news on this, or better yet, a workaround for now? I ran into the same issue, and I'm 100% stuck with no way forward that I can see. My...

Also, I'd like to point out that the message it gives is terribly unhelpful and not at all what the issue is. [The line in question](https://github.com/ingydotnet/git-subrepo/blob/73a01294bf1bef2e746d6c4c3054decf79dafa8f/lib/git-subrepo#L780) checks for ancestry, but...

@jgm: Ah, I wasn't sure about that, since I couldn't immediately see the blockquotes in the native format dump, and it doesn't generate them with Markdown target.

Actually, I think I misread the output slightly; it's not the the ordered / unordered switch that makes it actually nest the output, it's either sufficient level of nesting, or...

Some more testing suggests it's "sufficient amount of nesting" that makes it work properly, and the "sufficient amount" is actually determined by the level of indentation in the source Markdown....