From: Nick Dokos <nicholas.dokos@hp.com>
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-odt/org-export errors/paths
Date: Thu, 07 Jul 2011 16:57:07 -0400 [thread overview]
Message-ID: <6038.1310072227@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Thu\, 07 Jul 2011 16\:46\:57 EDT." <5955.1310071617@alphaville.americas.hpqcorp.net>
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Matt Price <moptop99@gmail.com> wrote:
>
> > Hi Jambunathan,
> >
> > I tried emacs -Q -L /home/matt/src/org-mode/lisp -L /home/matt/src/org-mode/contrib/lisp/
> > but the exporter still isn't working for me. The debug log is attached -- I wanted to leave the escaped characters intact. C-h v shows that org-export-backends is in fact defined:
> >
> > org-export-backends is a variable defined in `org-exp.el'.
> > Its value is (odt docbook html beamer ascii latex)
> >
> > but the backtrace looks to me like org doesn't quite understand that.
> >
> > thanks Jambunathan.
> > matt
> >
>
> The fault seems to be with org-footnote, not with org-odt, but it's hard
> to see where things go wrong because you've loaded compiled code for
> that. Can you try again with uncompiled code not only for org-odt but
> for everything else as well?
>
... and maybe try a simpler org file without footnotes and see if that
works. And maybe post the org-file with footnotes that makes org fail
(suitably sanitized). And if I think of anything else, I'll let you
know :-)
Nick
next prev parent reply other threads:[~2011-07-07 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 16:55 org-odt/org-export errors/paths Matt Price
2011-07-07 17:26 ` Jambunathan K
2011-07-07 20:29 ` Matt Price
2011-07-07 20:46 ` Nick Dokos
2011-07-07 20:57 ` Nick Dokos [this message]
2011-07-07 21:09 ` Matt Price
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=6038.1310072227@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.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).