From: Carsten Dominik <carsten.dominik@gmail.com>
To: Skip Collins <skip.collins@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
Jambunathan K <kjambunathan@gmail.com>
Subject: Re: odt export version conflict on emacs for mac os x
Date: Sat, 31 Aug 2013 08:04:34 +0200 [thread overview]
Message-ID: <513951A8-0878-4133-AD2B-36FAC7D4B98C@gmail.com> (raw)
In-Reply-To: <CABUh-75sxwC3kkWq_imFSVJdkDawrv=qZMhJtUx8xMFLoq_Geg@mail.gmail.com>
Hi,
can someone please summarize this discussion for me and tell me what action is required?
Thank you!
- Carsten
On 29.8.2013, at 20:25, Skip Collins <skip.collins@gmail.com> wrote:
> Jambunathan K <kjambunathan@gmail.com> wrote:
>>> After I do an ODT export, many ox-odt variables are duplicated with
>>> old variable names:
>>> | [-]-\ Group Org Export ODT
>>> | | |--- Option Org Odt Schema Dir
>>> | | |--- Option Org Odt Content Template File
>>
>> Above ones come from NEW exporter, ox-odt.el
>>
>>> | | |--- Option Org Export Odt Schema Dir
>>> | | |--- Option Org Export Odt Content Template File
>>
>> Above ones come from LEGACY exporter. Not used by ox-odt.el.
>>
>> This is confusing but the behaviour is expected and NOT BUGGY.
>
> Thank you for clarifying a confusing situation. I am not sure why I
> assumed that the org-export-odt variables were the newer ones.
>
> Suggestion for maintainers: a new, separate customization group, with
> appropriate pointers in the documentation, would be helpful.
>
next prev parent reply other threads:[~2013-08-31 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 13:50 odt export version conflict on emacs for mac os x Skip Collins
2013-08-19 20:09 ` Skip Collins
2013-08-20 7:53 ` Christian Moe
2013-08-20 17:05 ` Skip Collins
2013-08-29 5:05 ` Jambunathan K
2013-08-29 18:25 ` Skip Collins
2013-08-31 6:04 ` Carsten Dominik [this message]
2013-08-31 6:28 ` Jambunathan K
2013-08-31 7:26 ` Achim Gratz
2013-08-31 8:47 ` Christian Moe
2013-08-31 16:53 ` Achim Gratz
2013-08-31 8:54 ` Carsten Dominik
2013-08-31 10:16 ` Jambunathan K
2013-08-29 4:55 ` Jambunathan K
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=513951A8-0878-4133-AD2B-36FAC7D4B98C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=skip.collins@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).