emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: export to odt is not per default in the export menu
Date: Fri, 08 Apr 2016 11:07:31 +0200	[thread overview]
Message-ID: <m2y48ov57w.fsf@christianmoe.com> (raw)
In-Reply-To: <87mvp4fr74.fsf@ericabrahamsen.net>


This question pops up fairly often. I suggest that ODT should be
provided out of the box. It is clearly in demand. It meets the needs of
a whole segment of users that need to work with office software. Sure,
nothing prevents them from using it by adding a brief line to their init
file. But why not advertise it? It's a major feature and it works well.

Yours,
Christian

Eric Abrahamsen writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> Hi
>>
>> When I use org-export-dispatch, then a list of possible formats pop up
>> but odt is not among them. Only if I explicitly call
>> org-odt-export-to-odt
>>
>> once, then this command pops up in the list. How
>> can I change this behaviour and have the odt export function in the
>> list??
>
> Somewhere in your init files, put (require 'ox-odt). Then it will always
> be available. Take a look at the other ox-* files, many of them are
> useful enough to always load by default.
>
> E

  reply	other threads:[~2016-04-08  9:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08  8:14 export to odt is not per default in the export menu Uwe Brauer
2016-04-08  8:19 ` Eric Abrahamsen
2016-04-08  9:07   ` Christian Moe [this message]
2016-04-08  9:38     ` Eric Abrahamsen
2016-04-08  9:40       ` Xebar Saram
2016-04-08 18:06         ` Eduardo Mercovich
2016-04-10  8:23       ` Nicolas Goaziou
2016-04-10  9:45         ` Eric Abrahamsen
2016-04-10 11:29           ` Christian Moe
2016-04-13  2:18         ` Eduardo Mercovich
2016-04-08 10:08   ` Uwe Brauer

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=m2y48ov57w.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).