Ihor Radchenko <yanta...@posteo.net> writes: > May you please elaborate why this breaking change is going to lead to > significant improvement? How is using "," worse than using "|"? Either > way, strings containing the separator will become problematic and need > to be escaped. Moreover, using "|" may lead to interpreting the output > as Org tables, which may be surprising to users.
Thank you for the review! The change of the separator was a lazy move on my part. I appologize. I changed the separator because I could not figure out how to make Org behave sanely. The problem is not specific to Lua: src_elisp{"3, 2, 1, and go!"} {{{results(=3\, 2\, 1\, and go!=)}}} Why Org is escaping commas here? In other words, should my tests expect \-escapes in front of commas, or is that a bug? I am attaching a V2 of the patch that: - does not modify the separator anymore (resulting in 3 failing tests) - adds one more test (which is just a sanity check, you can ignore it) - fixes Lua code indentation (as indented by the Lua major mode) Thank you for your guidance. Rudy -- "Be especially critical of any statement following the word 'obviously.'" --- Anna Pell Wheeler, 1883-1966 Rudolf Adamkovič <rud...@adamkovic.org> [he/him] Studenohorská 25, 84103 Bratislava, Slovakia, European Union