[rinh]

What

In a table cell, an escaped pipe (\|) is now a literal |, the way GitHub renders it. Before this change it started a new column.

Source	Before	After
`--part 1|2`	two cells, broken code span	--part 1|2 (code)
a | b	two cells	a | b

Why

GFM documents \| as the way to put a pipe into a table cell, including inside inline code. It is common in tables of CLI options such as --part 1|2. QuickMD split such a row into one cell too many: the rest of the row moved one column to the right, and the backticks ended up in different cells.

How

• parseTableRow scans the row character by character instead of calling components(separatedBy: "|"). Only an unescaped | separates cells.
• \| becomes | in the cell text, inside code spans too (GFM). \\| is an escaped backslash followed by a real separator. Other escapes stay in the text for the inline renderer, as before.
• Leading and trailing pipes, padding, and trimming of trailing empty cells work as before. Table detection is unchanged.

Testing

• New ParserTests.testEscapedPipeStaysInsideItsCell: escaped pipe inside a code span and in plain text, \\|, and an escaped pipe at the end of a cell.
• xcodebuild … test: all 757 tests pass. The Release build and the -DAPPSTORE build both succeed.
• Manually checked in the app with a table of CLI commands: each command stays in one cell and shows 1|2.
• CHANGELOG has a line under [Unreleased].

🤖 Generated with Claude Code

[b451c]

Thanks again, @rinh! Merged (via #45) with one small follow-up: GitHub never splits a row at a pipe right after a backslash, even after \\ (path\\| c stays one cell there, and `p\\|q` shows p\|q), so the scanner now does the same. Your test is kept and extended. It will ship in the next release.

[b451c]

Shipped in v1.14.0: GitHub download and Homebrew (brew upgrade --cask b451c/quickmd/quickmd) now; the Mac App Store update follows after Apple's review.