John MacFarlane

> a table header needs to be followed by a delimiter row, otherwise it is not a table. Yes, and that's what this parser expects. The difficulty is that this...

OK, back to the drawing board. Here's another case to keep in mind: ``` - `a|b` - | - ``` This does parse -- as a table. Hm, I wonder...

Literal pipes in GitHub's pipe tables formerly needed to be escaped, even inside code backticks; let's see if that's still the case: | test | table | | ---- |...

Aha. You need a trailing newline in `input` in your program above. That's why it's not parsing as a table.

Original case also works with the workaround; you just need to ensure that all lines are terminated with newline characters.

I don't think the workaround will have any bad consequences: it just means that nothing will be interpreted as a table if it can be interpreted as any other kind...

Hand-coding is the way to go; I want dependencies to be light. It would be good to measure the performance impact of this, though. And it might turn out to...

Thanks for checking this. I'm not too worried about it if it doesn't significantly affect the most common case, where filenames don't have these special characters. I guess it's just...

Maybe backslash-escapes are the most straightforward. However, this would mean that backslashes in the filename would always be escaped (doubled); I suppose this could be an issue for Windows users?

I suppose then we'd still have an ambiguity involving filenames that start and end with `"`, wouldn't we? Maybe another approach would be to percent-escape `:` and `-` (and I...