emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Org Mode <emacs-orgmode@gnu.org>
Cc: 22182-done@debbugs.gnu.org, "B.V. Raghav" <bvraghav@iitk.ac.in>
Subject: Re: bug#22182: 24.5; Org Mode Export
Date: Thu, 17 Dec 2015 14:41:41 +0100	[thread overview]
Message-ID: <87bn9p9oq2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2r3inxq7b.fsf@newartisans.com> (John Wiegley's message of "Tue, 15 Dec 2015 15:11:20 -0800")

Hello,

John Wiegley <jwiegley@gmail.com> writes:

> Forward report to Org mailing list, and closing from Emacs bug tracker.
>
>>>>>> B V Raghav <bvraghav@iitk.ac.in> writes:
>
>> 1. I open an ORG file, with template headers, default and texinfo template.
>
>> 2. I write some simple ascii data to a few tree nodes.
>
>> 3. Export using <C-c> <C-e> i i for texinfo
>
>> And it crashes with following backtrace (Non-printable characters of
>> backtrace have been replaced with .):
>>> Debugger entered--Lisp error: (wrong-type-argument listp #("Modeling notes
>>> for Mged" 0 23 (:parent (#1)))) org-element-set-contents(#("Modeling notes
>>> for Mged" 0 23 (:parent (#0)))) apply(org-element-set-contents #("Modeling
>>> notes for Mged" 0 23 (:parent (#0))) nil) #[(s)

This kind of error was reported already. IIRC, it is a problem on user's
side (often a mixed installation). 

In particular, upgrade from Org included in Emacs to current stable
revision requires special care (e.g., Org must not be loaded when
upgrading the package).


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-12-17 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r3infhcf.fsf@think.bvr.lan>
2015-12-15 23:11 ` bug#22182: 24.5; Org Mode Export John Wiegley
2015-12-17 13:41   ` Nicolas Goaziou [this message]
2015-12-18  0:16     ` B.V. Raghav

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=87bn9p9oq2.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=22182-done@debbugs.gnu.org \
    --cc=bvraghav@iitk.ac.in \
    --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).