From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Parsing property drawers in subtree scope exports Date: Thu, 06 Jul 2017 19:19:11 +0200 Message-ID: <87inj57ab4.fsf@nicolasgoaziou.fr> References: <87y3s84mxp.fsf@nicolasgoaziou.fr> <87injc2l95.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53570) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dTAQz-0005au-EN for emacs-orgmode@gnu.org; Thu, 06 Jul 2017 13:19:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dTAQu-00043k-E7 for emacs-orgmode@gnu.org; Thu, 06 Jul 2017 13:19:21 -0400 Received: from relay5-d.mail.gandi.net ([217.70.183.197]:47221) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dTAQu-000430-73 for emacs-orgmode@gnu.org; Thu, 06 Jul 2017 13:19:16 -0400 In-Reply-To: (Kaushal Modi's message of "Thu, 06 Jul 2017 17:08:32 +0000") 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: Kaushal Modi Cc: emacs-org list Hello, Kaushal Modi writes: > Thanks. That works. Just curious though.. if one specifies certain keywords > to be exporter specific keywords in the backend definition in > :options-alist, it is evident that those keywords are specifically for > export. Should the requirement to have "EXPORT_" prefix before them be > relaxed? Do you foresee things not happening right if we started doing > that? I do. User may not be aware of keywords defined in export back-ends. As a consequence user-defined properties could interfere with export specific ones. E.g., ":TITLE:" and ":EXPORT_TITLE:" could mean different things. > - Make use of the inbuilt EXPORT_ prefix and get rid of the "HUGO_" prefix > I need exactly that. My idea is to have a single Org file with one subtree > per a blog post. So each subtree will have meta data about that post, like > data, categories, etc. I meant that you probably need to expand the buffer in order to get the properties. Once this is done, you can return to the original narrowing. Regards, -- Nicolas Goaziou 0x80A93738