Re: words starting with call_ confuse C-c C-c and export

[Eric Schulte <schulte.eric@gmail.com>]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Nicolas Goaziou <n.goaziou@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)?
>

Why don't we exclude whitespace from names.  Do you think that would be
sufficient?

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D