No solution, but sympathy. Syntax risk is difficult to prevent in Org I wonder if we can come up with incremental improvements that involve more universal escaping, quoting, nesting, etc. mechanisms somehow?
(This is /not/ intended to be a sly plug for my universal syntax proposal. That's not intended to replace all existing syntax, but only to be used for future syntax. However, I do have a list of parsing risk issues on the list someplace that might be a reference.) -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com === Bigotry against people with serious diseases is still bigotry.