From: Aaron Ecay <aaronecay@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [BUG] Infloop in org-element-inlinetask-parser
Date: Sun, 29 Jun 2014 01:27:32 -0400 [thread overview]
Message-ID: <CAFcZrT3SN0iP-=W-_e776dDD+g8JW_2a7hbuAh9a6t0o3eY0=g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Hello,
In the latest checkout of master, I am seeing an infloop in
org-element-inlinetask-parser. This originates when that function
calls back into org-element-at-point to look for a property drawer,
which moves the point back before the beginning of the inlinetask and
then attempts to re-enter org-element-inlinetask-parser.
The attached files reproduce the bug. Eval the .el file in emacs -Q
(after changing the path to your checkout of the org sources) and then
attempt to open the .org file.
The latest commit in my checkout of org is:
commit 2824502e2ebe2744e5f53acabb5b3b04f9a391b9
Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Date: Sat Jun 28 00:28:45 2014 +0200
org-element: Fix cache corruption when altering a drawer
My emacs is a recent-ish trunk build; latest commit:
commit cacabe3a49dbb3da268e93d88ad0f21924f26bed
Author: Kelvin White <kelvin.white77@gmail.com>
Date: Thu Jun 19 13:22:31 2014 -0400
Update comments in erc-format-@nick to reflect changes in last merge.
Thanks,
Aaron
[-- Attachment #2: bug.el --]
[-- Type: text/x-emacs-lisp, Size: 186 bytes --]
(let ((org-path "~/development/org-mode/"))
(add-to-list 'load-path (concat org-path "lisp/")))
(require 'org)
(require 'org-inlinetask)
;; optional:
(setq org-element-use-cache nil)
[-- Attachment #3: bug.org --]
[-- Type: application/vnd.lotus-organizer, Size: 185 bytes --]
next reply other threads:[~2014-06-29 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 5:27 Aaron Ecay [this message]
2014-06-29 13:27 ` [BUG] Infloop in org-element-inlinetask-parser Nicolas Goaziou
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='CAFcZrT3SN0iP-=W-_e776dDD+g8JW_2a7hbuAh9a6t0o3eY0=g@mail.gmail.com' \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).