Marked Share: TextBundle export reverses all inline code spans

Viewed 26

Marked 3.2.3 (1217), Mac App Store, macOS 26.5

I'm trialing Marked 3 and just started testing Marked Share. I noticed that every backticked code span in a published document is in the wrong place, and after some testing I'm fairly sure it's in the TextBundle/TextPack generator, not the server.

Here's a minimal repro. Save this as test.md:

First span: `alpha`. Second span: `bravo`. Third span: `charlie`.

When I export it as a TextBundle (File → Export → TextBundle), or publish it to Marked Share, then open text.md inside the bundle:

  • Expected: alpha, bravo, charlie
  • Actual: charlie, bravo, alpha

The order is exactly reversed. With N code spans, the first shows the last span's text, the second shows the second-to-last, and so on. I tested with a real 37-span document and every backticked reference was wrong, while the surrounding prose was untouched.

I also noticed that tables in the bundle come back reformatted with padded, aligned columns. That and the reversal are the only differences from the source, which makes me think a table-formatting pass lifts code spans out to protect them and restores them last-in-first-out. Preview, HTML export, and PDF export are all fine; it's just the TextBundle path.

Live examples on Marked Share (the content is whatever the bundle contained):

https://markedb.in/ktvfh — three spans, no table

https://markedb.in/mdet7 — five spans plus a table

(Not sharing the 37-span document because it contains too much sensitive information.) Hit Raw on any of them to see the reversed source.

2 Answers

Yes, this is an issue in Marked. It's been fixed in 3.2.4, but that update may not have hit the MAS yet. Give me a couple days and I'll make sure the fix is fully deployed.

Confirmed fixed in 3.2.4 (1218). Exported a five-span file with a table as a TextBundle — all spans in source order, table cells correct. Thank you.

Small leftover: the bundle still pads table columns, and it measures the padding before restoring the code spans, so cells with backticks come out short. Cosmetic only.