From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: File local variables and export? Date: Wed, 6 May 2009 09:25:21 +0200 Message-ID: References: <878wlcfzr0.fsf@sparse.dyndns.org> <0BC5E66D-AA3F-4D43-B830-E36C2EFFB434@gmail.com> <87k54vbmyx.fsf@sparse.dyndns.org> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1bVU-0005sj-1B for emacs-orgmode@gnu.org; Wed, 06 May 2009 03:25:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1bVO-0005qu-BF for emacs-orgmode@gnu.org; Wed, 06 May 2009 03:25:30 -0400 Received: from [199.232.76.173] (port=58233 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1bVO-0005qq-8I for emacs-orgmode@gnu.org; Wed, 06 May 2009 03:25:26 -0400 Received: from mx20.gnu.org ([199.232.41.8]:41410) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M1bVN-0004RQ-Lb for emacs-orgmode@gnu.org; Wed, 06 May 2009 03:25:25 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M1bVN-0005jE-1k for emacs-orgmode@gnu.org; Wed, 06 May 2009 03:25:25 -0400 Received: by ewy6 with SMTP id 6so5882762ewy.42 for ; Wed, 06 May 2009 00:25:24 -0700 (PDT) In-Reply-To: <87k54vbmyx.fsf@sparse.dyndns.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jason Riedy Cc: emacs-orgmode@gnu.org On May 5, 2009, at 5:15 PM, Jason Riedy wrote: > And Carsten Dominik writes: >>> I can smuggle the value in by adding an entry to >>> org-export-plist-vars referring to >>> org-export-latex-image-default-option and pulling the value from >>> the plist, but that feels incorrect. >> >> To me it sounds correct, actually. I have added this, and will >> add other variables as needed. > > I was thinking about using file locals to pass arguments along to > custom functions... Carrying a central registry feels funny. Why > do you prefer org-export-plist-vars? Because the buffer being exported is not current when doing the conversion. I know that this is less than ideal, but it is historically how the exporter developed. Another possibility would be a way to put arbitrary values into the property list that is used during export. The #+OPTIONS line does this, and we could have something like #+EXPORT_PROPS: :value "key" ....... which would add properties to the options property list, and any function could access their values. - Carsten