On Wed, Jun 13, 2018 at 7:56 PM Berry, Charles wrote:
> #+RESULTS:
> : # of src block names: 3
> : Number of Seconds: 0.0498
>
>
> #+RESULTS:
> : # of src block names: 68
> : Number of Seconds: 2.1021
>
> #+RESULTS:
> : # of src block names: 200
> : Number of Seconds:15.4018
>
>
>
Hi Chuck,
Thanks for your continued help and interest in this issue.
Here are the results from the timing test using your code:
| # Blocks | w/o noweb | noweb | NESTED noweb |
|--+---+---+---|
|3 | 0.05 | | 0.33 |
| 13 | 0.15
> On Jun 12, 2018, at 10:32 PM, Ken Mankoff wrote:
>
>
>
> On Wed, Jun 13, 2018 at 12:12 AM Berry, Charles wrote:
> > On Jun 12, 2018, at 2:30 PM, Ken Mankoff wrote:
> >
> > Based on the profiling, I think the reason it takes 1 minute is because the
> > code blocks use <> blocks?
>
> I d
On Wed, Jun 13, 2018 at 12:12 AM Berry, Charles wrote:
> > On Jun 12, 2018, at 2:30 PM, Ken Mankoff wrote:
> >
> > Based on the profiling, I think the reason it takes 1 minute is because
> the code blocks use <> blocks?
>
> I do not see this.
>
> It takes a bit longer to run the noweb example yo
> On Jun 12, 2018, at 2:30 PM, Ken Mankoff wrote:
>
> Based on the profiling, I think the reason it takes 1 minute is because the
> code blocks use <> blocks?
I do not see this.
It takes a bit longer to run the noweb example you gave with 200 `baz' src
blocks, but nothing crazy - like 10
As an MWE, I can test with "emacs -Q" and the following org file:
#+PROPERTY: header-args :eval never-export
# (setq org-export-use-babel t)
#+BEGIN_SRC emacs-lisp :results none
(org-babel-do-load-languages
'org-babel-load-languages
'((shell . t)))
#+END_SRC
#+BEGIN_SRC sh :results org
On Tue, Jun 12, 2018 at 11:07 PM Berry, Charles wrote:
>
> > On Jun 12, 2018, at 12:41 PM, Ken Mankoff wrote:
> >
> > Hi Chuck,
> >
> > It looks fine to me. I see:
> >
> > Name: fig:foo
> > Lang: python
> > Properties:
> > :header-args:eval never-export
> > :header-args:python
> On Jun 12, 2018, at 12:41 PM, Ken Mankoff wrote:
>
> Hi Chuck,
>
> It looks fine to me. I see:
>
> Name: fig:foo
> Lang: python
> Properties:
> :header-args:eval never-export
> :header-args:python nil
> Header Arguments:
> :cache no
> :eval
Hi Chris,
Thanks for the hint. I didn't think to profile. This may be useful, but I'm
not sure how to interpret the results, which are:
- command-execute 15852 79%
- call-interactively 15852 79%
- funcall
Hi Chuck,
It looks fine to me. I see:
Name: fig:foo
Lang: python
Properties:
:header-args :eval never-export
:header-args:python nil
Header Arguments:
:cache no
:eval never-export
:exports results
:hlines no
:noweb yes
:results file replace
:session discharge_ts
:tangle no
-k.
On Tue, Jun 1
> On Jun 12, 2018, at 7:01 AM, Ken Mankoff wrote:
>
> I'm trying to export a file to LaTeX. It takes about one minute. The
> file is 12000 lines long and has 200 code blocks. I have set:
>
> #+PROPERTY: header-args :eval never-export
>
That is the right idiom. Of course, you have to refres
Hello, Ken!
Ken Mankoff (mank...@gmail.com) 2018-06-12:
> Is there a way to speed up exporting?
I may be jumping to conclusions here, and if so, please excuse me. Have
you tried profiling the export? (As in M-x profiler-start, run the
export, then M-x profiler-report?) This can shed a surprising
I'm trying to export a file to LaTeX. It takes about one minute. The
file is 12000 lines long and has 200 code blocks. I have set:
#+PROPERTY: header-args :eval never-export
which means, I think, no babel blocks should evaluate.
(setq org-export-use-babel t) seems to be the culprit. If I set it
13 matches
Mail list logo
