I'm running into this issue now.
One thing I noticed is that if you have broken links (and
org-export-with-broken-links is t), org-id-update-id-locations will be
run for every broken link it finds. This turns out to be quite slow and
unnecessary since no files will have changed in between
org-id-
Hi Nicolas,
Thank you for providing suggestions about the appropriate tool. I've
profiled it, examined the variables you suggested, but am not sure what
next steps to take. I hope it is OK that I post questions about this on
this list...
On Thu, May 28, 2020 at 5:17 AM Nicolas Goaziou
wrote:
>
Hello,
I see a few misconceptions here.
Ken Mankoff 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
On Wednesday, 27 May 2020 at 17:24, Ken Mankoff wrote:
> Can anyone offer suggestions why it reports scanning 22 files, and how
> to speed it up since no code should be evaluated?
Anecdotally, I have the impression that all org buffers in the current
Emacs instance are scanned as well as the files
Hello,
When I eval `(org-icalendar-combine-agenda-files nil)`, it takes about 15
seconds.
Some strange messages in the *Messages* buffer include:
22 files scanned, 7 files contains IDs and in total 23 IDs found.
But my `org-agenda-files` variable only contains 12 files and no #+INCLUDE
statem
