From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [ox] possible to modify org-export-document-properties OTG Date: Sun, 22 Mar 2015 02:34:20 +0100 Message-ID: <87r3shvmqr.fsf@gmx.us> References: <87vbi030eb.fsf@gmx.us> <87k2yg115l.fsf@nicolasgoaziou.fr> <87iodytfza.fsf@gmx.us> <877fua3q0z.fsf@nicolasgoaziou.fr> <87vbhtvqtz.fsf@gmx.us> <87384x4z7z.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54421) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZUmj-0005ae-VA for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 21:34:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZUmf-0001k6-0K for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 21:34:37 -0400 Received: from plane.gmane.org ([80.91.229.3]:35818) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZUme-0001jg-Pa for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 21:34:32 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YZUmd-0006Ff-D4 for emacs-orgmode@gnu.org; Sun, 22 Mar 2015 02:34:31 +0100 Received: from 46.166.186.232 ([46.166.186.232]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Mar 2015 02:34:31 +0100 Received: from rasmus by 46.166.186.232 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 22 Mar 2015 02:34:31 +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@gnu.org Nicolas Goaziou writes: > Rasmus writes: > >> I /think/ that is what I would like. But I don't understand the what you >> mean concretely: would you have something like: >> >> (:subject "SUBJECT" nil nil space parsed) > > > (:subject "SUBJECT" nil nil parsed) > > `parsed' behavior implies `space' anyway, since we're talking about > secondary strings. Is that always the case? I guess.. >> I agree this is a difficult problem. Personally, I think it is fine to >> consider a keyword as a keyword and nothing more, and not consider content >> within a keyword. However, as I recall, John had a post a while back >> about mapping over bold in CAPTIONS or something like that. > > `org-element-map' can find objects in captions, with an optional > argument. If turns out to be important, perhaps it would also be possible to map keyword objects with an non-default argument. -- Don't panic!!!