From: Eric Schulte <eric.schulte@gmx.com>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: bug in org-element-parse-buffer, affects new HTML exporter
Date: Mon, 10 Sep 2012 17:34:22 -0600 [thread overview]
Message-ID: <87har5v4e9.fsf@gmx.com> (raw)
Hi,
Save the following text to an Org-mode file,
- one :: first
- two :: - second
- three :: third
and then call the `org-element-parse-buffer' function from within that
buffer. The following error will result. This breaks the new export
engine for buffers containing text like the above.
Thanks,
,----
| Debugger entered--Lisp error: (wrong-type-argument stringp nil)
| string-match("[[:alnum:]]" nil)
| org-list-get-list-type(25 ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) ((1) (16 . 1) (34 . 16)))
| org-element-plain-list-parser(34 ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)))
| org-element--current-element(34 nil nil ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)))
| org-element--parse-elements(25 34 nil ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) nil nil (item (:bullet "- " :begin 16 :end 34 :contents-begin 25 :contents-end 34 :checkbox nil :counter nil :hiddenp nil :structure ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) :post-blank 0 :tag ("two"))))
| org-element--parse-elements(1 51 item ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) nil nil (plain-list (:type descriptive :begin 1 :end 51 :contents-begin 1 :contents-end 51 :structure ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) :post-blank 0) (item (:bullet "- " :begin 1 :end 16 :contents-begin 10 :contents-end 16 :checkbox nil :counter nil :hiddenp nil :structure ((1 0 "- " nil nil "one" 16) (16 0 "- " nil nil "two" 34) (34 0 "- " nil nil "three" 51)) :post-blank 0 :tag ("one") :parent #0) (paragraph (:begin 10 :end 16 :contents-begin 10 :contents-end 16 :post-blank 0 :parent #1) "first\n"))))
| org-element--parse-elements(1 51 nil nil nil nil (section (:begin 1 :end 51 :contents-begin 1 :contents-end 51 :post-blank 0)))
| org-element--parse-elements(1 51 first-section nil nil nil (org-data nil))
| org-element-parse-buffer()
| eval((org-element-parse-buffer) nil)
| eval-expression((org-element-parse-buffer) nil)
| call-interactively(eval-expression nil nil)
`----
--
Eric Schulte
http://cs.unm.edu/~eschulte
next reply other threads:[~2012-09-10 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 23:34 Eric Schulte [this message]
2012-09-12 13:50 ` bug in org-element-parse-buffer, affects new HTML exporter 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=87har5v4e9.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
/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).