Nick, I meant to include (setq org-export-backends '(odt)) in my .emacs
file. I did that, and now I get the odt exporter as an option when I do
C-c C-e.
I usually try no to use things that make changes to my .emacs file
direcly because I generate my .emacs file from an .org file (through
Manfred Lotz manfred.lotz at arcor.de writes:
Are you calling (require 'ox-odt) somewhere in your config? Or
configuring `org-export-backends'? ODT export isn't loaded by default,
you'll have to load it explicitly by one of those two methods.
This should be included in the manual. From
Hello,
Julian Burgos jul...@hafro.is writes:
Manfred Lotz manfred.lotz at arcor.de writes:
Are you calling (require 'ox-odt) somewhere in your config? Or
configuring `org-export-backends'? ODT export isn't loaded by default,
you'll have to load it explicitly by one of those two methods.
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.
Nicolas Goaziou writes:
Hello,
Julian Burgos jul...@hafro.is writes:
Manfred Lotz manfred.lotz at arcor.de writes:
Are you calling (require 'ox-odt)
Just thinking how to things easier for noobs like me. :)
Julian M. Burgos 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.
Nicolas Goaziou writes:
Hello,
Julian Burgos jul...@hafro.is
Julian M. Burgos jul...@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,
--
Ok, I see what you mean. So I should do
(setq org-export-backends '(odt)) or something like that. Fair enough. :)
Nicolas Goaziou writes:
Julian M. Burgos jul...@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
Julian M. Burgos jul...@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
On Tue, May 7, 2013 at 11:32 AM, Nick Dokos ndo...@gmail.com wrote:
Julian M. Burgos jul...@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
John Hendy jw.he...@gmail.com writes:
#+begin_quote
3 Installation
PP
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
Hi there,
Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt
doesn't work. zip program is available. When I do =C-c C-e= the
*Org Export Dispatcher* buffer pops up but showing nothing related to
odt. When now typing =o o= I get =Invalid Key=.
Any idea what's going wrong.
--
Manfred Lotz manfred.l...@arcor.de writes:
Hi there,
Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt
doesn't work. zip program is available. When I do =C-c C-e= the
*Org Export Dispatcher* buffer pops up but showing nothing related to
odt. When now typing =o o= I get
On Sun, 21 Apr 2013 22:29:10 +0800
Eric Abrahamsen e...@ericabrahamsen.net wrote:
Manfred Lotz manfred.l...@arcor.de writes:
Hi there,
Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt
doesn't work. zip program is available. When I do =C-c C-e= the
*Org Export
13 matches
Mail list logo
