Do you think it makes sense to treat unfinished parens/brackets/braces/... in language meant to be used as a markup as errors? Existing ones like Markdown tend to allow them, but I guess requiring users to prefix those meant as normal text with \ could often avoid those "dumb" mistakes where you later realize you forgot to match parens while reading finished document
In that case they would potentially write e.g. \(-= - I wonder whether such things are written in notes/docs enough to be inconvenient
Last example is not really a problem - I don't care about contents of code blocks
Do you think it makes sense to treat unfinished parens/brackets/braces/... in language meant to be used as a markup as errors? Existing ones like Markdown tend to allow them, but I guess requiring users to prefix those meant as normal text with
\could often avoid those "dumb" mistakes where you later realize you forgot to match parens while reading finished documentOr - how often do you write single paren, outside of literal block, where you actually mean to do so?
I could see someone using a smiley-face (-=
Or, russian exclamation marks)))))
orrr for example a bash script in a backtics block
In that case they would potentially write e.g.
\(-=- I wonder whether such things are written in notes/docs enough to be inconvenientLast example is not really a problem - I don't care about contents of code blocks