From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: [PARSER] Why not add properties to type 'org-data'? Date: Sat, 07 Sep 2013 11:28:46 +0200 Message-ID: <87li399e0h.fsf@gmail.com> References: <87y57be0zv.fsf@gmail.com> <87zjrrytan.fsf@gmail.com> <87txhzdkrc.fsf@gmail.com> <87li39yuf1.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37415) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VIEpH-0001L7-AT for emacs-orgmode@gnu.org; Sat, 07 Sep 2013 05:29:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VIEp9-0000mW-BQ for emacs-orgmode@gnu.org; Sat, 07 Sep 2013 05:29:07 -0400 Received: from plane.gmane.org ([80.91.229.3]:38121) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VIEp9-0000mK-4h for emacs-orgmode@gnu.org; Sat, 07 Sep 2013 05:28:59 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VIEp7-0003Eb-GA for emacs-orgmode@gnu.org; Sat, 07 Sep 2013 11:28:57 +0200 Received: from e178188125.adsl.alicedsl.de ([85.178.188.125]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 07 Sep 2013 11:28:57 +0200 Received: from tjolitz by e178188125.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 07 Sep 2013 11:28:57 +0200 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: > Hello, > > Thorsten Jolitz writes: > >> But sometimes, when only the parse-tree is needed, not the exporter >> framework, it would indeed be useful if that highest level element the >> others refer to as parent (org-data) would have some kind of unique >> name/id. >> >> What would be the cost of introducing just one single unique attribute >> like: >> >> ,------------------------------------------------------------------------- >> | (org-data (:input-file /my/file.org) (section (:begin 1 :end 52 ...))) >> `------------------------------------------------------------------------- >> >> or >> >> ,------------------------------------------------------------------------- >> | (org-data (:ID 08AF34b12) (section (:begin 1 :end 52 ...))) >> `------------------------------------------------------------------------- >> >> to make different parse trees distinguishable (and associated to the >> parsed file)? > > There is no real cost in this case. Though, note that :input-file would > not make for a unique identifier. Yes, :input-file plus (exact) :date would probably do the job as unique identifier(s). > On the other hand, what prevents you, once you have the parse tree, from > tagging it with all the attributes you need? Nothing really, I just thought that the space after 'org-data' is a bit wasted and that it would be generally usefull to put some unique 'parse-tree-id' there instead of just nil. But it may be better to keep the core functionality as clean and simple as possible and add this kind of info later on if necessary. -- cheers, Thorsten