Re: Problem with noweb-ref property

[Andreas Leha <andreas.leha@med.uni-goettingen.de>]

Eric Schulte <eric.schulte@gmx.com> writes:
>>>>
>>>> However correct performance is more important than fast performance.
>>>> I've just pushed up a patch which fixes the bug you've described, and
>>>> hopefully doesn't slow down the tangling process too significantly.
>>>>
>>
>> Hi Eric,
>>
>> unfortunately, for me it does result in a considerably slow down.
>> (Well, I did not bisect this time but still suspect the commit you
>> mention in this thread.)
>>
>> As a test case you can still use
>> http://pastebin.com/c42jS1Be
>> from my last post on this matter and expand the first source block.
>>
>> Sorry to ask again:  Would it be possible to speed things up again or to
>> make the :noweb-ref feature optional?
>>
>
> Hi Andreas,
>
> I've just pushed up a new variable to the git repository.  To enable the
> faster regexp-based method of noweb expansion (which is not able to
> resolve noweb-ref header arguments inherited from sub-tree or file-wide
> properties) put the following in your config.
>
> (setq *org-babel-use-quick-and-dirty-noweb-expansion* t)
>
> Best,
>

Hi Eric,

thanks for this quick-and-dirty fix ;-)  Works great!

Cheers,
Andreas