Re: [PARSER] Why not add properties to type 'org-data'?

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Thorsten Jolitz <tjolitz@gmail.com> writes:

> Wouldn't it make sense to replace 
>
> ,----------------------------------------------
> | (org-data nil (section (:begin 1 :end 52 ...)))
> `----------------------------------------------
>
> with something like
>
> ,-------------------------------------------------------------------------
> | (org-data (:id-or-name file001 :input-file /my/file.org :author me :date
> | 01-01-2013 :description my planning data) (section (:begin 1 :end 52
> | ...)))
> `-------------------------------------------------------------------------
>
> ?

This is way beyond parser's attributions. For example, getting the right
date means that every SETUPFILE keyword should be inspected. INCLUDE
keywords too. And some macros could get expanded in the process.

Also keep in mind that some keywords, e.g. DESCRIPTION, are defined and
made special at the export framework level (see
`org-export-options-alist'). There are just regular keywords to the
parser. IOW, for the parser, there is no difference between

  #+DESRCIPTION: something

and

  #+FOO: something

At one point, I thought about combining parse tree and information
channel, much like what you're suggesting, but in `ox.el'. It would give
something like an "Org closure" wrapping both contents and environment
together.

But I discarded that idea, as it was very artificial: the minute the
closure was created, it was splitted again so it could get processed.


Regards,

-- 
Nicolas Goaziou