emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Brady Trainor <algebrat@uw.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Which `odt-content' variable should I use? Why are there two?
Date: Mon, 27 Jan 2014 11:32:10 +0100	[thread overview]
Message-ID: <87a9ehemvp.fsf@bzg.ath.cx> (raw)
In-Reply-To: <loom.20140126T201233-241@post.gmane.org> (Brady Trainor's message of "Sun, 26 Jan 2014 19:20:46 +0000 (UTC)")

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

  reply	other threads:[~2014-01-27 10:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 19:20 Which `odt-content' variable should I use? Why are there two? Brady Trainor
2014-01-27 10:32 ` Bastien [this message]
2014-01-27 13:47 ` 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=87a9ehemvp.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=algebrat@uw.edu \
    --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).