From: Aaron Ecay <aaronecay@gmail.com>
To: Neuwirth Erich <erich.neuwirth@univie.ac.at>
Cc: Bastien <bzg@altern.org>,
"emacs-orgmode@gnu.org Mode" <emacs-orgmode@gnu.org>
Subject: Re: Further problems with export
Date: Wed, 13 Mar 2013 19:47:33 -0400 [thread overview]
Message-ID: <87ehfic162.fsf@gmail.com> (raw)
In-Reply-To: <28DFE91C-313B-42EC-981F-000EDCAFDE4C@univie.ac.at>
Hi Erich,
org-exp-blocks only works with the old exporter, not the new one. It
was removed from the master branch git repo in commit ee3b3eb on Mar 2.
I’m not clear what version of org you are using (seems it’s not master,
as the org-e-foo files have been renamed ox-foo), but you should beware
of picking up an old version of some elisp files from the org-mode that
comes bundled with emacs.
I’ve heard
(http://thread.gmane.org/gmane.emacs.orgmode/64972/focus=65013) that the
new exporter supports in some way the org-exp-blocks functionality, but
I still don’t know how exactly that works.
I don’t know what is causing your error specifically, but maybe making
sure the lisp files you are loading all come from the same version of
org will help. I *think* that you should make sure that the
installation directory for org comes first in the ‘load-path’ variable
then using just (require 'org) as Bastien suggests should do the trick.
You might need to install the org files to a directory outside of the
Emacs.app bundle, then manually add that to ‘load-path’.
--
Aaron Ecay
next prev parent reply other threads:[~2013-03-13 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 13:05 Further problems with export Neuwirth Erich
2013-03-13 14:16 ` Bastien
2013-03-13 22:46 ` Neuwirth Erich
2013-03-13 22:56 ` Bastien
2013-03-13 23:25 ` Neuwirth Erich
2013-03-14 7:04 ` Achim Gratz
2013-03-14 9:21 ` Neuwirth Erich
2013-03-14 19:15 ` Achim Gratz
2013-03-13 23:47 ` Aaron Ecay [this message]
2013-03-14 1:15 ` Neuwirth Erich
2013-03-14 1:25 ` Neuwirth Erich
2013-03-14 1:50 ` Neuwirth Erich
2013-03-14 2:06 ` Bastien
2013-03-14 5:11 ` Nick Dokos
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=87ehfic162.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=erich.neuwirth@univie.ac.at \
/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).