From: David Masterson <dsmasterson92630@outlook.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Infinite recursion ?
Date: Tue, 22 Sep 2020 18:08:42 -0700 [thread overview]
Message-ID: <SJ0PR03MB561563279C01B2E0C4B27F759B380@SJ0PR03MB5615.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87lfh1ucyt.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Tue, 22 Sep 2020 10:02:02 -0400")
Nick Dokos <ndokos@gmail.com> writes:
> David Masterson <dsmasterson92630@outlook.com> writes:
>
>> Haven't figured this out yet, but I seem to be hitting an "infinite
>> recursion" bug that eventually dies when it runs out of memory.
>>
>> The scenario (so far) is trying to change an Org tag in the agenda
>> (':'). The command gives me the tags that I then edit and save whereupon
>> it sits in an infinite recursion until it hits a limit in Emacs. If I
>> quit, the files seem to have been updated, but the Agenda isn't. I'm
>> still trying to figure out how to debug this. Setting debug-on-quit was
>> not consistent and didn't seem to have a large list of function calls
>> (ie. the recursion). Any ideas?
>>
>> This is Emacs 26.3 with Orgmode 9.4. I'm also using Org-Super-Agenda
>> from Melpa (20200310.1337).
>>
>> Side question that might be related: org-agenda started positioning
>> itself at the end of the agenda rather than the beginning after building
>> the agenda. I don't think I changed something for this. What could
>> cause this?
>
> What's the error message? Did you try setting `debug-on-eror'? Does that give
> a more useful backtrace?
The error has to do with org-agenda-property-list. I'm going to file
this as a bug.
--
David Masterson
prev parent reply other threads:[~2020-09-23 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 22:19 Infinite recursion ? David Masterson
2020-09-22 4:31 ` David Masterson
2020-09-22 8:50 ` Eric S Fraga
2020-09-22 14:02 ` Nick Dokos
2020-09-22 16:09 ` Nick Dokos
2020-09-23 1:08 ` David Masterson [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=SJ0PR03MB561563279C01B2E0C4B27F759B380@SJ0PR03MB5615.namprd03.prod.outlook.com \
--to=dsmasterson92630@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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).