From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Salazar Subject: Re: wrong type argument listp... org-element-set-contents Date: Sat, 8 Aug 2015 08:55:26 -0400 Message-ID: References: <8737zuck6o.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11380d502f8d4a051ccc440e Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37072) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZO3eq-0005Xi-Qo for emacs-orgmode@gnu.org; Sat, 08 Aug 2015 08:55:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZO3ep-0006rF-L3 for emacs-orgmode@gnu.org; Sat, 08 Aug 2015 08:55:28 -0400 Received: from mail-pa0-x22b.google.com ([2607:f8b0:400e:c03::22b]:33360) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZO3ep-0006pt-CR for emacs-orgmode@gnu.org; Sat, 08 Aug 2015 08:55:27 -0400 Received: by pabyb7 with SMTP id yb7so74131497pab.0 for ; Sat, 08 Aug 2015 05:55:26 -0700 (PDT) In-Reply-To: <8737zuck6o.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode , mail@nicolasgoaziou.fr --001a11380d502f8d4a051ccc440e Content-Type: text/plain; charset=UTF-8 Sure, I'll try that. I'm not quite sure how to figure out what argument org-export-dispatch takes. Something like this? (org-reload (org-export-dispatch 'html)) On Sat, Aug 8, 2015 at 3:29 AM, Nicolas Goaziou wrote: > Hello, > > Peter Salazar 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 > --001a11380d502f8d4a051ccc440e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sure, I'll try that.=C2=A0I'm not quite sure how t= o figure out what argument=C2=A0org-export-dispatch takes. Something like t= his?=C2=A0(org-reload (org-export-dispatch 'html))

=

On Sat, Aug 8, 20= 15 at 3:29 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>= wrote:
Hello,

Peter Salazar <cycleofsong@gmai= l.com> writes:

> I'm getting a strange error whenever I try to export an org file,<= br> > and I'm not sure how to track down the cause. It seemed to start w= hen I
> upgraded to org 8.3.1, but it's hard to tell because this is the f= irst
> time I've exported anything in a week or so.
>
> The error says:
> (wrong-type-argument listp #("Test document" 0 13 (:parent (= #1))))
>=C2=A0 =C2=A0org-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<= br> > 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

--001a11380d502f8d4a051ccc440e--