emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC PATCH 0/2] Make org-babel-tangle usable in after-save-hook on large org buffers
Date: Sun, 31 Jul 2022 14:43:15 +0800	[thread overview]
Message-ID: <87y1w9n5oc.fsf@localhost> (raw)
In-Reply-To: <cover.1644236545.git.yantar92@gmail.com>

Ihor Radchenko <yantar92@gmail.com> writes:

> I would like to send an experimental patch improving performance of
> org-babel-tangle.  The patch contains two major changes:
> 1. org-babel-tangle-single-block will not try to parse LINK to src
>    block when :comments is set to "no" and simple return nil in
>    relevant slot of the parsed src block structure.
> 2. org-babel-expand-noweb-references cache will be saved between the
>    function calls (reset on buffer edits)

Applied onto main via 0435fea9a and 0d3bf2ed4.


      parent reply	other threads:[~2022-07-31  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 12:31 [RFC PATCH 0/2] Make org-babel-tangle usable in after-save-hook on large org buffers Ihor Radchenko
2022-02-07 12:31 ` [RFC PATCH 1/2] org-babel-tangle-single-block: Do not create comment link when not requested Ihor Radchenko
2022-02-07 12:31 ` [RFC PATCH 2/2] org-babel-expand-noweb-references: Cache block info Ihor Radchenko
2022-07-31  6:43 ` Ihor Radchenko [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:

  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=87y1w9n5oc.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).