From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: ICS agenda export exceeds max-specpdl-size probably because of org-depend (org-edna same?)
Date: Fri, 28 Feb 2020 15:29:27 +0100 [thread overview]
Message-ID: <2020-02-28T15-27-46@devnull.Karl-Voit.at> (raw)
In-Reply-To: 2020-02-24T14-50-59@devnull.Karl-Voit.at
This week, the error re-appeared.
* Karl Voit <devnull@Karl-Voit.at> wrote:
>
> Thanks for the advice. I ran three test runs in order to find out how output is
> affected:
>
>
> Testrun with disabled org-depend:
> emacs-snapshot --batch --load /home/vk/.emacs.d/init.el --eval '(progn (my-export-agenda))
> 261.95s user 1.57s system 99% cpu 4:24.01 total
>
> → I got a result without error
>
>
> Testrun with enabled org-depend:
> emacs-snapshot --batch --load /home/vk/.emacs.d/init.el --eval '(progn (my-export-agenda))'
> 117.58s user 1.46s system 99% cpu 1:59.60 total
>
> → much faster result without error :-) (probably caching?)
>
>
> revoking the two suggested changes and do another test run with org-depend, expecting error:
> emacs-snapshot --batch --load /home/vk/.emacs.d/init.el --eval '(progn (my-export-agenda))'
> 114.38s user 1.53s system 99% cpu 1:56.33 total
>
> → much faster result without error (contrary to expection)
>
>
> → the two setting changes do not have an effect for now regarding
> error/no error due to the fact that I can not reproduce the
> error.
>
> Retrying when error re-appears.
- setting `org-agenda-before-write-hook' to nil
- `org-icalendar-include-body': 42
- enabled org-depend
: emacs-snapshot --batch --load /home/vk/.emacs.d/init.el --eval '(progn (my-export-agenda))'
→ did not finish after running for 4 hours (aborted)
- setting `org-agenda-before-write-hook' to nil
- `org-icalendar-include-body': 42
- *disabled org-depend*
→ produced output within 4min39s
- setting `org-agenda-before-write-hook' to default
- `org-icalendar-include-body': to default
- disabled org-depend
→ produced output within 2min07s
Any other test you want me to run?
--
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/
prev parent reply other threads:[~2020-02-28 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 12:36 ICS agenda export exceeds max-specpdl-size probably because of org-depend (org-edna same?) Karl Voit
2020-02-11 8:03 ` Bastien
2020-02-11 13:33 ` Karl Voit
2020-02-11 13:38 ` Bastien
2020-02-11 14:07 ` Karl Voit
2020-02-19 15:54 ` Karl Voit
2020-02-19 16:03 ` Bastien
2020-02-20 9:25 ` Karl Voit
2020-02-20 10:25 ` Bastien
2020-02-20 14:26 ` Karl Voit
2020-02-20 17:58 ` Bastien
2020-02-21 8:29 ` Karl Voit
2020-02-23 13:32 ` Bastien
2020-02-23 16:21 ` Karl Voit
2020-02-24 8:46 ` Bastien
2020-02-24 13:55 ` Karl Voit
2020-02-24 20:29 ` Bastien
2020-02-28 14:29 ` Karl Voit [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=2020-02-28T15-27-46@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).