Hello, Eric Schulte <schulte.e...@gmail.com> writes:
> Nicolas Goaziou <n.goaz...@gmail.com> writes: >> Just to be clear, I thought about making parens mandatory in inline >> Babel call syntax. Underscore is overloaded already: underline, >> subscript... >> > > I'm open to this change. In fact, they are already mandatory. The problem is different. Current regexp is: "\\([^\n]*?\\)call_\\([^()\n]+?\\)\\(\\[\\(.*?\\)\\]\\|\\(\\)\\)(\\([^\n]*?\\))\\(\\[\\(.*?\\)\\]\\)?" In particular, name is \\([^()\n]+?\\), and can include whitespace characters. Therefore "call_name (args)" is valid. Isn't it too much permissive in the context of an Org (i.e. textual) document? Also, couldn't we limit names to alphanumeric characters and, maybe, some puctuation (e.g. hypen)? Regards, -- Nicolas Goaziou
