From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: odt export not working Date: Tue, 7 May 2013 13:46:47 -0500 Message-ID: References: <20130421154204.29323d38@arcor.com> <87txn0neix.fsf@ericabrahamsen.net> <20130421163157.25e33c90@arcor.com> <878v3qevq8.fsf@gmail.com> <87ip2udbyw.fsf@gmail.com> <87fvxylphy.fsf@pierrot.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57918) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UZmua-0001zd-1N for emacs-orgmode@gnu.org; Tue, 07 May 2013 14:46:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UZmuX-0005RE-MY for emacs-orgmode@gnu.org; Tue, 07 May 2013 14:46:51 -0400 Received: from mail-la0-x232.google.com ([2a00:1450:4010:c03::232]:53166) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UZmuX-0005Qu-Ej for emacs-orgmode@gnu.org; Tue, 07 May 2013 14:46:49 -0400 Received: by mail-la0-f50.google.com with SMTP id fl20so925121lab.9 for ; Tue, 07 May 2013 11:46:47 -0700 (PDT) In-Reply-To: <87fvxylphy.fsf@pierrot.dokosmarshall.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos Cc: emacs-orgmode On Tue, May 7, 2013 at 11:32 AM, Nick Dokos wrote: > "Julian M. Burgos" 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 =E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2= =95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90 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 =3Dorg-export-backends=3D, 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 =3DC-h v=3D or =3DM-x help=3D 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 =3D(require 'ox-backend)=3D line for every exporter I want vs. the org-export-backends variable for this reason. John > > Nick > >> >> Nicolas Goaziou writes: >> >>> "Julian M. Burgos" writes: >>> >>>> Right... I did not saw it. And even if I did, I would not know that t= he >>>> 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 > >