From: Jambunathan K <kjambunathan@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Ken Mankoff <mankoff@gmail.com>
Subject: Re: Citations and references in ODT
Date: Sun, 19 Jan 2014 11:16:53 +0530 [thread overview]
Message-ID: <878uuc7cc2.fsf@gmail.com> (raw)
In-Reply-To: 86wqhz1umf.fsf@freeenv.ad.medctr.ucla.edu
Aric Gregson <aorchid@mac.com> writes:
> From http://permalink.gmane.org/gmane.emacs.orgmode/80832
> OpenDocument export failed: Symbol's function definition is void:
> org-element-cache-reset
> I also receive this error the first time that I try to open an org
> file. I can open the file if I try another time.
Are you still stuck here or you made some repairs and stuck elsewhere.
The above error has nothing to do ox-odt.el or ox-jabref.el. It says
your org-element.el is coming from some unexpected path. The problem is
usually because of wrong installation.
> Jambunathan has any ideas as to why his exporter is not working with my
> set-up.
It is difficult for me to imagine how you set up things. (There are so
many moving parts). All I can say is this: "Not related to odt/jabref
exporters. Something is related to how you have setup things". Nothing
more.
You will have better luck if
1. You start emacs with a blank .emacs
2. Install Org from ELPA.
Once you have a working ox-odt.el setup, then you can make additional
modifications to that setup and install ox-jabref.el.
----------------------------------------------------------------
Your best debug tools are
1. M-x find-library
2. M-x locate-library
3. M-x list-load-path-shadows.
You can run the above commands vis-a-vis the following libraries
1. org-loaddefs
2. org-compat
3. org-element.el
and investigate *for yourself* whether the paths are getting "mixed up".
If you analyse the output, you will understand what I mean. Most likely
there are stale or non-existent .elc files or the .elc files were
generated against a stale library.
IMO, starting from scratch (i.e., an empty .emacs) and installing Org
via M-x list-packages is a sure way to have a working setup with minimal
fuss.
next prev parent reply other threads:[~2014-01-19 5:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 18:10 Citations and references in ODT Ken Mankoff
2014-01-10 20:24 ` Aric
2014-01-11 4:31 ` Jambunathan K
2014-01-11 12:59 ` Ken Mankoff
2014-01-11 13:53 ` Jambunathan K
2014-01-11 14:13 ` Ken Mankoff
2014-01-14 0:18 ` Aric Gregson
2014-01-13 2:51 ` Ken Mankoff
2014-01-13 6:31 ` Nick Dokos
2014-01-13 15:49 ` Ken Mankoff
2014-01-14 0:16 ` Aric Gregson
2014-01-14 9:16 ` Jambunathan K
2014-01-14 19:10 ` Aric Gregson
2014-01-15 12:26 ` Ken Mankoff
2014-01-16 21:31 ` Aric Gregson
2014-01-19 5:46 ` Jambunathan K [this message]
2014-01-21 1:25 ` Aric Gregson
2014-01-23 14:18 ` Jambunathan K
2014-01-23 14:31 ` Jambunathan K
2014-01-14 8:56 ` Jambunathan K
2014-01-14 0:59 ` Aric Gregson
2014-01-14 9:24 ` Jambunathan K
2014-01-14 19:14 ` Aric Gregson
2014-01-11 4:38 ` Jambunathan K
2014-01-11 12:35 ` Christopher Kotfila
2014-01-14 0:17 ` Aric Gregson
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=878uuc7cc2.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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).