From: Achim Gratz <Stromeko@NexGo.DE>
Subject: Re: org-reload and new exporter
Date: Wed, 14 Nov 2012 12:03:57 +0000 (UTC) [thread overview]
Message-ID: <loom.20121114T125616firstname.lastname@example.org> (raw)
Andreas Leha <andreas.leha <at> med.uni-goettingen.de> writes:
> *Messages* does not show anything suspicious:
Indeed. Since the org-export backends clearly are reloaded, some of the later
reloads must subvert them. I'd assume that this is due to something else from
contrib you have loaded, but you could simply reload org step by step in the
order that org-reload does and check where the export backends drop out.
> I am installing to a custom location. Is that the problem here?
I don't think so, I do that all the time. But I'm not using nearly as many
packages from contrib...
next prev parent reply other threads:[~2012-11-14 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 8:45 org-reload and new exporter Andreas Leha
2012-11-14 9:35 ` Achim Gratz
2012-11-14 9:49 ` Andreas Leha
2012-11-14 12:03 ` Achim Gratz [this message]
2012-11-14 13:04 ` Andreas Leha
2012-11-14 14:07 ` Nicolas Goaziou
2012-11-15 8:52 ` Andreas Leha
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).