emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: odt export not working
Date: Tue, 07 May 2013 12:32:41 -0400	[thread overview]
Message-ID: <87fvxylphy.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: xgzd2t2n58l.fsf@hafnfirdingur.hafro.is

"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.

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

  reply	other threads:[~2013-05-07 16:35 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 [this message]
2013-05-07 18:46                 ` John Hendy
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=87fvxylphy.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).