From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Which `odt-content' variable should I use? Why are there two? Date: Mon, 27 Jan 2014 11:32:10 +0100 Message-ID: <87a9ehemvp.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7jUJ-00032q-Ki for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:32:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W7jUE-0007Vy-4G for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:32:19 -0500 Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:44950) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W7jUD-0007Vo-TN for emacs-orgmode@gnu.org; Mon, 27 Jan 2014 05:32:14 -0500 Received: by mail-we0-f180.google.com with SMTP id q59so4973690wes.39 for ; Mon, 27 Jan 2014 02:32:13 -0800 (PST) In-Reply-To: (Brady Trainor's message of "Sun, 26 Jan 2014 19:20:46 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Brady Trainor Cc: emacs-orgmode@gnu.org Hi Brady, Brady Trainor 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