diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-25 07:54:34 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-25 07:54:34 -0500 |
| commit | f3b583e67ec18345c2b5c988f452388894363d1e (patch) | |
| tree | d5e95df54cf379b275f422386fcc92036b338734 /tests/check-deps.el | |
| parent | bd2aa5705d94b7d403096c62637e64c479ea0de5 (diff) | |
| download | pearl-f3b583e67ec18345c2b5c988f452388894363d1e.tar.gz pearl-f3b583e67ec18345c2b5c988f452388894363d1e.zip | |
feat: render inline code spans verbatim in the Org buffer
A fetched description with markdown inside backticks — `**bold**`, `[text](url)`, `_italic_` — got its span contents converted along with the surrounding prose, so the Org buffer showed `*bold*` and `[[url][text]]` inside what should read as literal code. Markdown treats a code span as opaque; the converter didn't.
Both converters now tokenize code spans first and apply link/bold/italic conversion only to the text between them, keeping span contents literal. The md->org and org->md directions each split into an emphasis-only helper (pearl--md-emphasis-to-org, pearl--org-emphasis-to-md) called on the gaps, with the span passed through untouched. Keeping the split symmetric is what preserves the round-trip identity a fetch + no-edit push depends on.
A new test asserts the verbatim rendering for bold, link, and italic inside a span, plus emphasis still converting outside one and between two spans.
Diffstat (limited to 'tests/check-deps.el')
0 files changed, 0 insertions, 0 deletions
