From mboxrd@z Thu Jan 1 00:00:00 1970 From: Per Unneberg Subject: Re: behaviour of org-export--get-subtree-options vs inbuffer-options Date: Thu, 06 Nov 2014 09:58:47 +0100 Message-ID: <87sihwbt88.fsf@gmail.com> References: <877fzaj58j.fsf@gmail.com> <87oasl93w5.fsf@nicolasgoaziou.fr> Reply-To: Per Unneberg Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39615) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmIuF-000870-27 for emacs-orgmode@gnu.org; Thu, 06 Nov 2014 03:59:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XmIu8-0007TP-J3 for emacs-orgmode@gnu.org; Thu, 06 Nov 2014 03:59:03 -0500 Received: from mail-lb0-x22e.google.com ([2a00:1450:4010:c04::22e]:43418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmIu8-0007TI-9G for emacs-orgmode@gnu.org; Thu, 06 Nov 2014 03:58:56 -0500 Received: by mail-lb0-f174.google.com with SMTP id z11so30921lbi.5 for ; Thu, 06 Nov 2014 00:58:55 -0800 (PST) Received: from ubuntu-VirtualBox (130-229-48-229.scilifelab.ki.se. [130.229.48.229]) by mx.google.com with ESMTPSA id eg2sm2299895lbb.29.2014.11.06.00.58.54 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 06 Nov 2014 00:58:54 -0800 (PST) In-Reply-To: <87oasl93w5.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 05 Nov 2014 14:24:26 +0100") 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: Emacs-orgmode Hi, Nicolas Goaziou writes: > > Yes, you cannot have duplicate property names in the same property > drawer. OTOH you can append values to a property with :NAME+: syntax > (e.g. :EXPORT_LATEX_HEADER+:). You can also try to make everything fit > in a single line. > thanks for the clarifications and the pointer to the nifty :NAME+: syntax. It all makes sense now. I temporarily played around with a tentative alternative solution, in which I defined a derived backend with a modified template translator, modifying the property list sent to org-latex-template. Works, but slightly more cumbersome. Cheers, Per