From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Peter Salazar <cycleofsong@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: wrong type argument listp... org-element-set-contents
Date: Sat, 08 Aug 2015 09:29:19 +0200 [thread overview]
Message-ID: <8737zuck6o.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAE+_6TynFGBt=oQ5gn_SHPvygXpJZvB8Oe--yp+XxP91L1-hwQ@mail.gmail.com> (Peter Salazar's message of "Fri, 7 Aug 2015 23:11:22 -0400")
Hello,
Peter Salazar <cycleofsong@gmail.com> writes:
> I'm getting a strange error whenever I try to export an org file,
> and I'm not sure how to track down the cause. It seemed to start when I
> upgraded to org 8.3.1, but it's hard to tell because this is the first
> time I've exported anything in a week or so.
>
> The error says:
> (wrong-type-argument listp #("Test document" 0 13 (:parent (#1))))
> org-element-set-contents(#("Test document" 0 13 (:parent (#0))))
>
> I was able to figure out that the error only occurs when I have an org file
> with document data, e.g. a line like:
>
> #+TITLE: Test document
>
> When I remove that line as well as #+AUTHOR etc, then it exports fine. With
> that line it, it won't export to HTML, LaTeX, or text.
>
> Any suggestions on how to figure out what part of my configuration is
> causing the problem? Here's the complete Backtrace:
> https://gist.github.com/fe45c4d42d52f0ce0e42
I cannot reproduce the problem. Could you provide a backtrace using an
uncompiled Org? (i.e., using `org-reload' with an argument).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-08-08 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 3:11 wrong type argument listp... org-element-set-contents Peter Salazar
2015-08-08 7:27 ` Kyle Meyer
2015-08-08 7:29 ` Nicolas Goaziou [this message]
2015-08-08 12:55 ` Peter Salazar
2015-08-08 13:27 ` Nicolas Goaziou
2015-08-08 15:30 ` Peter Salazar
2015-08-08 15:59 ` Kyle Meyer
2015-08-08 16:53 ` Peter Salazar
2015-08-08 17:09 ` Kyle Meyer
2015-08-09 3:43 ` Peter Salazar
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=8737zuck6o.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=cycleofsong@gmail.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).