Hello back,
> My concern has nothing to do with users. > It is about third-party parsers that will have to implement Elisp parser > on top of Org parser. I'm not sure I get your point, as third-party parsers already had to deal with emacs regexps in links. Or are you talking about parsing the plist's properties? "Ihor Radchenko" <[email protected]> writes: > Julien Dallot <[email protected]> writes: > >>> That's the problem. "simple plist" brings with it all the Elisp syntax, >>> including all kinds of weird escape rules. > >> It is a problem. But as users rarely look into links and as links should be >> generated automatically in any good workflow, I do not find it is too big of >> a problem. > > My concern has nothing to do with users. > It is about third-party parsers that will have to implement Elisp parser > on top of Org parser.
