From: Jambunathan K <kjambunathan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Skip Collins <skip.collins@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: odt export version conflict on emacs for mac os x
Date: Sat, 31 Aug 2013 11:58:36 +0530 [thread overview]
Message-ID: <87hae6s7aj.fsf@gmail.com> (raw)
In-Reply-To: 513951A8-0878-4133-AD2B-36FAC7D4B98C@gmail.com
Best way to explain is with an example:
1. emacs -Q
2. eval this
(add-to-list 'load-path "~/src/org-mode/lisp/")
(require 'org-loaddefs)
Ensure that there is org-loaddefs available from git path.
3. M-x load-library ox-odt.el
4. Ensure (featurep 'org-odt) reports nothing.
5. M-x customize-group org-export-odt.
6. See both legacy (org-export-odt-*) and new variables (org-odt-*)
being reported.
----------------------------------------------------------------
s/odt/latex/. The result will be the same
----------------------------------------------------------------
What needs to happen:
Put new things in new groups. I suggest org-export-ng or org-export-new
prefix for new exporter and backends.
Both the backend groups and the parent groups.
----------------------------------------------------------------
Long winded explanation:
-----------------------
Both the legacy and new exporters, declare SAME ":group
'org-export-backend" for but DIFFERENT user variables. Similar looking
variables is NOT guaranteed to have same functionality.
Vanialla Emacs "somehow" tracks the custom variables and it's group
/even if/ legacy exporters are NOT in the load path. So when new
exporter is loaded, the group displays BOTH the LEGACY and NEW
variables.
org-odt.el uses
(defgroup org-export-odt nil
"Options specific for ODT export of Org-mode files."
:tag "Org Export ODT"
:group 'org-export
:version "24.1")
(defcustom org-export-odt-content-template-file nil
"Template file for \"content.xml\".
The exporter embeds the exported content just before
\"</office:text>\" element.
If unspecified, the file named \"OrgOdtContentTemplate.xml\"
under `org-odt-styles-dir' is used."
:type 'file
:group 'org-export-odt
:version "24.1")
)
ox-odt.el uses
(defgroup org-export-odt nil
"Options for exporting Org mode files to ODT."
:tag "Org Export ODT"
:group 'org-export)
(defcustom org-odt-content-template-file nil
"Template file for \"content.xml\".
The exporter embeds the exported content just before
\"</office:text>\" element.
If unspecified, the file named \"OrgOdtContentTemplate.xml\"
under `org-odt-styles-dir' is used."
:type '(choice (const nil)
(file))
:group 'org-export-odt
:version "24.1")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> 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:26 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
2013-08-31 6:28 ` Jambunathan K [this message]
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=87hae6s7aj.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).