emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Help speeding up Org iCal export
Date: Thu, 28 May 2020 14:17:42 +0200	[thread overview]
Message-ID: <875zcgz21l.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874ks0aotm.fsf@gmail.com> (Ken Mankoff's message of "Wed, 27 May 2020 17:24:53 -0700")


I see a few misconceptions here.

Ken Mankoff <mankoff@gmail.com> writes:

> When I eval `(org-icalendar-combine-agenda-files nil)`, it takes about
> 15 seconds.

OK. You may want to profile this, or use ELP.

> Some strange messages in the *Messages* buffer include:
> 22 files scanned, 7 files contains IDs and in total 23 IDs found.

You may have set `org-icalendar-store-UID' somehow.

> But my `org-agenda-files` variable only contains 12 files and no
> #+INCLUDE statements.

ID scanning is not limited to agenda files. Org also scans files known
to contain ID. E.g., if, during the session, you insert an ID in
"foo.org", later scans (in the same session) will include "foo.org".

See `org-id-files' (internal variable), and `org-id-extra-files', which
may contain even more files.

> There are also several dozen lines of
> org-babel-exp process sh at position 74770...
> org-babel-exp process sh at position 74830...
> org-babel-exp process sh at position 75147...
> ...
> org-babel-exp process sqlite at position 27700...
> org-babel-exp process sqlite at position 27704...
> org-babel-exp process sh at position 27604...
> org-babel-exp process sh at position 27617...
> org-babel-exp process sh at position 27691...
> org-babel-exp process translate at position 27970...
> (and with bash, python, emacs-lisp, and other languages). When I view for example the only #BEGIN_SRC translate block in any of my files it is just a test in my notes file:
> #+BEGIN_SRC translate :src en :dest da
> This is a test
> I cannot eval it with C-c C-c because I have set ":eval no"
> system-wide with:

This is a red herring, IMO. The message above means the block is being
processed for export, not necessarily evaluated. In order to know how to
handle the block, Org needs to process it.

>   (setq org-babel-default-header-args
> 	(cons '(:eval . "no")
> 	      (assq-delete-all :eval org-babel-default-header-args)))
> Sometimes the Messages contain confirmation that a code block is disabled:
> org-babel-exp process plantuml at position 27719...
> Evaluation of this plantuml code block is disabled.
> org-babel-exp process plantuml at position 27762...
> Evaluation of this plantuml code block is disabled.

Here, it tries to evaluate the blocks, obviously, but eventually
doesn't, per your settings.

> But those blocks don't have any special header:
> #+begin_src plantuml :file tryout.png
> ...misc plantuml code here.
> #+end_src

I see no issue here. Org checks if it should evaluate it, and cannot.

> Can anyone offer suggestions why it reports scanning 22 files, and how
> to speed it up since no code should be evaluated?

See above. Instead of wild guesses, you could use an appropriate tool.


Nicolas Goaziou

  parent reply	other threads:[~2020-05-28 12:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28  0:24 [O] Help speeding up Org iCal export Ken Mankoff
2020-05-28  8:11 ` Eric S Fraga
2020-05-28 12:17 ` Nicolas Goaziou [this message]
2020-05-28 14:06   ` Ken Mankoff
2022-01-20 22:57     ` Josh Moller-Mara

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=875zcgz21l.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \


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