Code fencing in markdown export
planned
T
Tim Nevits
I noticed that in Markdown export, code fencing doesn't always start on a new line. It often comes after
**Assistant**:
, ie:Assistant
: ```While I can't find anything in the markdown spec explicitly forbidding this, the open fencing is ignored and rendering failed in the 3 markdown renderers I tried:
* Obsidian
Daniel Nguyen
planned
Oh right. I think there should be a line break after the
Assistant
: mark