From: John Hendy <jw.hendy@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: odt export not working
Date: Tue, 7 May 2013 13:46:47 -0500 [thread overview]
Message-ID: <CA+M2ft-GzX-ASj0vOY-DA2z4DnKGxZz3V=H4Q0scA8RWyt=C7Q@mail.gmail.com> (raw)
In-Reply-To: <87fvxylphy.fsf@pierrot.dokosmarshall.org>
On Tue, May 7, 2013 at 11:32 AM, Nick Dokos <ndokos@gmail.com> wrote:
> "Julian M. Burgos" <julian@hafro.is> writes:
>
>> Ok, I see what you mean. So I should do
>> (setq org-export-backends '(odt)) or something like that. Fair enough. :)
>>
>
> That's *not* what Nicolas suggested and it's *not* what you should do.
>
> Just do
>
> C-h v org-export-backends
>
> and click the Customize link, then mark all the (additional) backends
> you want to use. Please read the documentation of the variable: simply
> setting it in the middle of an emacs session will *not* work.
Though, know that there's a difference in how backends are treated
when loading them via the two methods:[1]
#+begin_quote
3 Installation
══════════════
There are two ways to install export back-ends.
1. You may customize `org-export-backends' variable. It contains the
list of back-ends that should always be available.
2. You can also simply require the back-end libraries (e.g. `(require
'ox-icalendar)' for the iCalendar back-end). Note that with method 1,
the back-ends will be loaded only when the export framework is used
for the first time.
#+end_quote
[1] http://article.gmane.org/gmane.emacs.orgmode/65574
If you customize =org-export-backends=, the actual backend is not
loaded until you export for the first time per new Emacs session.
Mostly not a big deal, but try this out with the following minimal
config:
#+begin_src emacs-config-method-1
;; set load paths
;; set load dirs and global config options
(add-to-list 'load-path "~/.elisp/org.git/lisp/")
(add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
(setq org-export-backends (quote (odt)))
#+end_src
- emacs -Q
- M-x load-file RET ~/path/to/min-config
- M-x help RET v org-odt-TAB
- Note completions
Now try this:
#+begin_src emacs-config-method-2
;; set load paths
;; set load dirs and global config options
(add-to-list 'load-path "~/.elisp/org.git/lisp/")
(add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
(require 'ox-odt)
#+end_src
Repeat the steps above and note the difference. If you want to do any
customizing or (like me) use =C-h v= or =M-x help= to remember the
name of the variable you're looking for, you won't get auto-completion
as Org isn't aware of the variable until you actually use the exporter
the first time (use the first minimal config, export to ODT, and then
repeat the steps described and you'll see that the variables are now
known).
Anyway, just wanted to make sure this was well known. I've taken to
using a =(require 'ox-backend)= line for every exporter I want vs. the
org-export-backends variable for this reason.
John
>
> Nick
>
>>
>> Nicolas Goaziou writes:
>>
>>> "Julian M. Burgos" <julian@hafro.is> writes:
>>>
>>>> Right... I did not saw it. And even if I did, I would not know that the
>>>> package needed for loading the back-end for ODT is called ox-odt.
>>>
>>> You don't need to know that. The manual tells you to customize
>>> `org-export-backends' instead.
>>>
>>>
>>> Regards,
>
> --
> Nick
>
>
next prev parent reply other threads:[~2013-05-07 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 13:42 odt export not working Manfred Lotz
2013-04-21 14:29 ` Eric Abrahamsen
2013-04-21 14:31 ` Manfred Lotz
2013-05-07 11:01 ` Julian Burgos
2013-05-07 13:59 ` Nicolas Goaziou
2013-05-07 14:58 ` Julian M. Burgos
2013-05-07 15:33 ` Julian M. Burgos
2013-05-07 15:52 ` Nicolas Goaziou
2013-05-07 16:07 ` Julian M. Burgos
2013-05-07 16:32 ` Nick Dokos
2013-05-07 18:46 ` John Hendy [this message]
2013-05-07 20:02 ` Nick Dokos
2013-05-10 10:10 ` Julian M. Burgos
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='CA+M2ft-GzX-ASj0vOY-DA2z4DnKGxZz3V=H4Q0scA8RWyt=C7Q@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@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).