Re: Bug: inconsistent escaping of coderef regexp

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

Tom Gillespie <tgbugs@gmail.com> writes:

> We can decouple them, so not an issue. The attached patch implements
> the header arg equivalents of -r and -l without making any changes to the
> existing switch behavior.

This is already conflating the two. I'd like to solve the issue at hand
without having header args interfere at all.

This can happen later, after a discussion on the ML.

>> 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.
>
> I did a first pass implementation and realized that allowing users to
> specify coderef-regexp is a bad idea. The attached patch fixes the
> divergent behavior of org-bable-tangle-single-block and provides a
> standard way to specify a :coderef-prefix regexp so that empty
> comments can be stripped.

Would you mind answering my questions first? I still don't follow you
about the coderef prefix/regexp.

Regards,
-- 
Nicolas Goaziou