From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PARSER] Why not add properties to type 'org-data'?
Date: Sat, 07 Sep 2013 09:15:14 +0200 [thread overview]
Message-ID: <87li39yuf1.fsf@gmail.com> (raw)
In-Reply-To: <87txhzdkrc.fsf@gmail.com> (Thorsten Jolitz's message of "Thu, 05 Sep 2013 23:24:55 +0200")
Hello,
Thorsten Jolitz <tjolitz@gmail.com> 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.
On the other hand, what prevents you, once you have the parse tree, from
tagging it with all the attributes you need?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-09-07 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 15:34 [PARSER] Why not add properties to type 'org-data'? Thorsten Jolitz
2013-09-05 19:14 ` Nicolas Goaziou
2013-09-05 21:24 ` Thorsten Jolitz
2013-09-07 7:15 ` Nicolas Goaziou [this message]
2013-09-07 9:28 ` Thorsten Jolitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87li39yuf1.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).