Fix markdown parser handling of escaped backticks

[exedev-shelley]

Author: redbeard0531
Channel: #shelley
Link: https://discord.com/channels/1405685085923049482/1450334528210993295/1539715811122487517

---

Issue

The markdown parser doesn't handle escaped backticks correctly.

Example

The `Ran \`cmd\`` opener, the fenced output, and the `[Output truncated...]` footer are what Pi injects into the LLM's context for every bash call, on top of the raw tool result.

The escaped backticks within inline code blocks are not being parsed properly.

Attachments

• image0.jpg

[RedBeard0531]

For comparison

The Ran \cmd`opener, the fenced output, and the[Output truncated...]` footer are what Pi injects into the LLM's context for every bash call, on top of the raw tool result.

[RedBeard0531]

Hmm. I guess GitHub also doesn't handle it well so 🤷

[minikomi]

The official markdown "web dingus" also renders this inout without escapes

Edit: it seems like escaped backticks only work outside code blocks.

• docs

Within inline code blocks;

To include a literal backtick character within a code span, you can use multiple backticks as the opening and closing delimiters:

``There is a literal backtick (`) here.``

There is a literal backtick (`) here.

[philz]

There's no winning with markdown. Closing this for now.