From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] speed of continued source blocks
Date: Sun, 11 Dec 2011 21:00:41 +0100 [thread overview]
Message-ID: <87mxayq3o6.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87wra353rb.fsf@gmx.com
Hi Eric,
Eric Schulte <eric.schulte@gmx.com> writes:
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Hi Eric,
>>
>> thanks for looking into this providing a patch already!
>>
>>> I've just pushed up a patch which should speed up the collection of
>>> continued source blocks. Please let me know if the performance increase
>>> is sufficient for your example, if not we can look at more dramatic
>>> methods of optimization or possibly at making the collection of such
>>> blocks conditional.
>>
>> The speed looks very good already!
>
> Great, unless I hear back I'll assume this issue is resolved. Thanks
> for the stress testing.
>
>> But now org-babel-expand-src-block (as well es the source block
>> evaluation) seems not to expand the noweb references at all and more.
>> Is that a problem only on my side?
>>
>
> Thanks for catching this, I was only testing :noweb-ref references, not
> named code block references. I've just fixed this issue and added an
> exercising test case so this won't happen in the future.
>
> Please let me know if any problems remain.
>
> Cheers,
>
>>
>>
>>> One option to avoid this overhead could be to add the following
>>>
>>> #+PROPERTY: noweb no
>>>
>>> to the top of your Org-mode file.
>>
>> Since I heavily rely on the noweb references, this is not an option for me.
>>
>> Cheers,
>> Andreas
>>
>>
thanks a lot! Works great now.
Cheers,
Andreas
prev parent reply other threads:[~2011-12-11 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 23:30 [babel] speed of continued source blocks Andreas Leha
2011-12-11 16:53 ` Eric Schulte
2011-12-11 18:04 ` Andreas Leha
2011-12-11 19:04 ` Eric Schulte
2011-12-11 20:00 ` 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=87mxayq3o6.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).