From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: Karl Voit <news1142@Karl-Voit.at>, emacs-orgmode@gnu.org
Subject: Re: Endless loop in org--setup-collect-keywords (agenda, ...)
Date: Sat, 01 Nov 2014 11:58:15 +0100 [thread overview]
Message-ID: <87egtnchmg.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <2014-10-31T17-14-17@devnull.Karl-Voit.at> (Karl Voit's message of "Fri, 31 Oct 2014 17:18:15 +0100")
Hello,
Karl Voit <devnull@Karl-Voit.at> writes:
> Weird behaviour: yesterday I switched my init.el to OrgStruct and
> re-organized it a bit. Silly me thought it would also be a clever
> time to update my Org git repo.
>
> At many occasions, my Emacs 24.3.50.1 hangs in an endless loop. When
> I break it, I get following Backtrace:
>
> | Debugger entered--Lisp error: (quit)
> | org--setup-collect-keywords("^[ ]*#\\+\\(\\(?:ARCHIVE\\|C\\(?:ATEGORY\\|O\\(?:\\(?:LUMN\\|NSTANT\\)S\\)\\)\\|FILETAGS\\|LINK\\|PR\\(?:IORITIES\\|OPERTY\\)\\|S\\(?:E\\(?:Q_TODO\\|TUPFILE\\)\\|TARTUP\\)\\|T\\(?:AGS\\|\\(?:YP_T\\)?ODO\\)\\)\\):[ ]*\\(.*\\)")
> | org-set-regexps-and-options()
> | org-mode()
> | set-auto-mode-0(org-mode nil)
> | #[0 "\302\242\237\211\205.
> | [...]
>
> (Sorry for the long line)
>
> Do you have a clue if my update or my re-arrangement of my init.el
> could have caused this?
I think latest commit fixed it. Could you confirm it? Otherwise, I'll
need an ECM to reproduce it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-11-01 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 16:18 Endless loop in org--setup-collect-keywords (agenda, ...) Karl Voit
2014-10-31 20:36 ` Kyle Meyer
2014-11-01 9:41 ` Confirmed: Endless loop in org--setup-collect-keywords caused by commit 61a241f Karl Voit
2014-11-01 10:58 ` Nicolas Goaziou [this message]
2014-11-01 11:50 ` fixed: Endless loop in org--setup-collect-keywords (agenda, ...) Karl Voit
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=87egtnchmg.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=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).