From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: mentioning EXPORT_LATEX_HEADER in the latex header info node Date: Fri, 17 Nov 2017 11:48:53 +0000 Message-ID: References: <87o9o2ueex.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c0acac4ce71cb055e2c5299" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47539) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eFf8s-0000oh-El for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 06:49:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eFf8r-0000nn-MC for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 06:49:06 -0500 Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]:45824) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eFf8r-0000nM-GL for emacs-orgmode@gnu.org; Fri, 17 Nov 2017 06:49:05 -0500 Received: by mail-yw0-x234.google.com with SMTP id q37so1125006ywa.12 for ; Fri, 17 Nov 2017 03:49:05 -0800 (PST) In-Reply-To: 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" To: Alan Schmitt Cc: emacs-org list , Nicolas Goaziou --94eb2c0acac4ce71cb055e2c5299 Content-Type: text/plain; charset="UTF-8" On Fri, Nov 17, 2017, 4:35 AM Alan Schmitt wrote: > > It makes sense. Reading the text there, I'm a bit surprised: > > For example, `DATE' and `EXPORT_FILE_NAME' keywords become, > respectively, `EXPORT_DATE' and `EXPORT_FILE_NAME'. > > Is the `EXPORT_FILE_NAME' a real example (i.e., a node property that has > a global and subtree meaning with the same name)? > I haven't used #+EXPORT_FILE_NAME *keyword* when exporting files because the exported file name base name is taken from the Org file base name. But I have used that as a :EXPORT_FILE_NAME: *property* in subtrees many times, when doing subtree scoped exports, and it works great :) For subtree exports, it's kind of mandatory to set that property if you want to export different subtrees from the same Org file to different files. > -- Kaushal Modi --94eb2c0acac4ce71cb055e2c5299 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Nov 17, 2017, 4:35 AM A= lan Schmitt <alan.schm= itt@polytechnique.org> wrote:

It makes sense. Reading the text there, I'm a bit surprised:

For example, `DATE' and `EXPORT_FILE_NAME' keywords become,
respectively, `EXPORT_DATE' and `EXPORT_FILE_NAME'.

Is the `EXPORT_FILE_NAME' a real example (i.e., a node property that ha= s
a global and subtree meaning with the same name)?

I haven't used #+EXPORT_FILE_NAME *keyword* when expor= ting files because the exported file name base name is taken from the Org f= ile base name.=C2=A0

But I have used that as a :EX= PORT_FILE_NAME: *property* in subtrees many times, when doing subtree scope= d exports, and it works great :) For subtree exports, it's kind of mand= atory to set that property if you want to export different subtrees from th= e same Org file to different files.=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
--

Kaushal Modi

--94eb2c0acac4ce71cb055e2c5299--