Which `odt-content' variable should I use? Why are there two?

Which `odt-content' variable should I use? Why are there two?

[Brady Trainor]

I was browsing the customize group org-export-odt. 

I found two variables that seem to do the same thing. 

In org-odt.el, we have
  org-export-odt-content-template-file

while in ox-odt.el, we have 
  org-odt-content-template-file

Do I need to worry about this. Will org-export check both locations, or will
one take precedence somehow? (As in, if one is `nil', will it more or less
have no effect on the other?) 

I imagine I could do some print variable testing to discover on my own, but
also wanted to see if comments would be enlightening to my understanding in
general. 

- Brady 

(learning Emacs because I found Org-mode; "programmer") 

Re: Which `odt-content' variable should I use? Why are there two?

[Bastien]

Hi Brady,

Brady Trainor <algebrat@uw.edu> writes:

> I was browsing the customize group org-export-odt. 
>
> I found two variables that seem to do the same thing. 
>
> In org-odt.el, we have
>   org-export-odt-content-template-file
>
> while in ox-odt.el, we have 
>   org-odt-content-template-file
>
> Do I need to worry about this. Will org-export check both locations, or will
> one take precedence somehow? (As in, if one is `nil', will it more or less
> have no effect on the other?) 

Your Emacs comes with an old Org version, while you are using another
one, either as a package or from a directory.

You don't need to worry about this is M-x org-version RET shows that
you are using Org > 8.

> I imagine I could do some print variable testing to discover on my own, but
> also wanted to see if comments would be enlightening to my understanding in
> general. 

What might be confusing is that options generally use the same prefix
than the package they belong to: (require 'my-package-*) will load new
options with a prefix like my-package-*.

In Org, the export packages start as ox-* since 8.0, but the options
they define start with org-export-* and not ox-*.  Using org-export-*
as the prefix for all Org export packages felt too much.

HTH,

-- 
 Bastien

Re: Which `odt-content' variable should I use? Why are there two?

[Jambunathan K]

Brady Trainor <algebrat@uw.edu> writes:

> I was browsing the customize group org-export-odt.


The old exporter and the new exporters share the same custom group.  So
you are seeing the old and new variables in the custom buffer.  (IMO
this is a bug.)

----------------------------------------------------------------

NEW variables do NOT have an extra "export" in their names
==========================================================

If you are using org > 8.0, the variables that you are interested in
should come from ox-odt.el.

M-x find-library ox-odt
M-<
C-s defcustom


(defcustom org-odt-prettify-xml nil
           ^^^^^^^
(defcustom org-odt-schema-dir
           ^^^^^^^

Note that NEW variables don't have "export" in their names.  Except for
change in the prefix, the functionality is for most part the same.

----------------------------------------------------------------

Migrate: Use search and replace
================================

So, a simple renaming in your .emacs should suffice for migrating your
old settings to the new settings.

C-x C-f .emacs
M-% org-export-odt- org-odt-
C-x C-s