From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: nicholas.dokos@hp.com,
Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [bug] error in html export: backend not defined
Date: Tue, 01 Mar 2011 16:39:10 -0500 [thread overview]
Message-ID: <11944.1299015550@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Eric S Fraga <e.fraga@ucl.ac.uk> of "Tue, 01 Mar 2011 20:24:56 GMT." <8762s2y4fb.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Hi,
>
> I notice that there has been a recent commit which affects export of org
> files. I have just needed to export an org file to HTML and get the
> following error:
>
> : if: Symbol's value as variable is void: backend
>
> The backtrace is:
>
> ,----
> | Debugger entered--Lisp error: (void-variable backend)
> | (eq backend (quote html))
> | (if (eq backend (quote html)) (progn (org-exp-bibtex-docites [...]
> | (when (eq backend (quote html)) (org-exp-bibtex-docites [...]
> | (save-window-excursion (setq oebp-cite-plist [...]
> | org-export-bibtex-preprocess()
> | run-hooks(org-export-preprocess-hook)
> | org-export-preprocess-string( [...] )
> | org-export-as-html(nil)
> | call-interactively(org-export-as-html)
> | org-export(nil)
> | call-interactively(org-export nil nil)
> `----
>
> For now, I am going to disable the invocation of the bibtex
> preprocessing as this appears to be the only place that =backend=
> appears.
>
It's likely that the only thing needed is to rename backend to
org-export-current-backend in contrib/lisp/org-exp-bibtex.el.
See commit 99675ffead44e32f4959909a657b88831fe33703.
Nick
next prev parent reply other threads:[~2011-03-01 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 20:24 [bug] error in html export: backend not defined Eric S Fraga
2011-03-01 21:39 ` Nick Dokos [this message]
2011-03-02 7:00 ` Eric S Fraga
2011-03-02 8:27 ` [patch] fix backend error for html export (was Re: [O] [bug] error in html export: backend not defined) Eric S Fraga
2011-03-02 17:17 ` Bastien
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=11944.1299015550@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=e.fraga@ucl.ac.uk \
--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).