Understood. I will start testing. Just out of curiosity, knowing full well that it will break the tangle, and also since I hadn't tried the quick and dirty flag, I ran it with this to see how long it took:
(setq org-babel-common-header-args-w-values nil) It went from 936 seconds (15 minutes) Down to 279 (4 minutes). Now I am wondering if it is worth converting my document *not* to use property inheritance... What would you folks do? Grant Rettke | ACM, ASA, FSF, IEEE, SIAM g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Thu, Jun 19, 2014 at 8:44 AM, Eric Schulte <schulte.e...@gmail.com> wrote: > Grant Rettke <g...@wisdomandwonder.com> writes: > >> I still want to be using org,, so my plan for now then is to write a >> pre-processing script for before org-babel-tangle is run that: >> >> 1. Checks each headline >> 2. Checks if there is a source block >> 3. If that source block doesn't have a noweb-ref name, and there is >> another source block under that >> headline, then "merge" it with the next source block of the same >> nature in that heading. >> >> That is off the top of my head, and I will try it by hand, first and >> see if it tangles the same result. >> >> Thoughts? > > Perhaps an easier workaround would be to customize the value of > `org-babel-common-header-args-w-values'. This variable determines which > header arguments are checked for in properties. If you remove all > header arguments from this variable which you know are not used in a > property, it may dramatically speed up tangle time. > > This may reduce the utility of some convenience functions, but should > not have too large of an impact on overall functionality. > > Best, > Eric > > -- > Eric Schulte > https://cs.unm.edu/~eschulte > PGP: 0x614CA05D (see https://u.fsf.org/yw)