emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with noweb-ref property
Date: Tue, 03 Jan 2012 11:07:53 +0100	[thread overview]
Message-ID: <87y5tpm746.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87k45ac6q4.fsf@gmx.com

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

     prev parent reply	other threads:[~2012-01-03 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29 19:13 Problem with noweb-ref property Tomas Grigera
2011-12-29 19:51 ` Eric Schulte
2011-12-29 23:16   ` Tomas Grigera
2012-01-02 12:32     ` Andreas Leha
2012-01-02 18:01       ` Eric Schulte
2012-01-03 10:07         ` Andreas Leha [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5tpm746.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).