Re: Bug: inconsistent escaping of coderef regexp

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

Tom Gillespie <tgbugs@gmail.com> writes:

>     After a bit of investigation I understand the issue better now.
> There are two problems here. One is an easy single line change,
> the other is a deeper issue, which is that it is impossible for the
> user to specify their own coderef regexp that can be used in both
> cases. No matter what change we make we are likely to break
> existing org files if users relied on one behavior and not the other.

[...]

> If we want a temporary fix, a patch is attached, but I would suggest
> against changing the behavior right now and instead work toward
> a new, more consistent system using header args.

If possible, I'd like not to conflate current issue with switches
deprecation, which needs to be discussed separately.

What do you mean by "it is impossible for the user to specify their own
coderef regexp that can be used in both cases"? In particular, what is
a coderef regexp in this context? I know about coderef format, but
I don't think users are supposed to provide a regexp here.

Regards,
-- 
Nicolas Goaziou