Eric Abrahamsen writes:
> Eike writes:
>
>> Hello list,
>>
>> I want to ask for help regarding elisp and org-elements. I like to
>> access the properties of all my headlines and I created the following
>> function (tree is the parsed tree) that collects them into an a-list:
>
> You could also ta
Eike writes:
> Hello list,
>
> I want to ask for help regarding elisp and org-elements. I like to
> access the properties of all my headlines and I created the following
> function (tree is the parsed tree) that collects them into an a-list:
You could also take a look at org-collector, in contri
Eike writes:
> Thanks a lot for the examples, they are very helpful! I first thought to
> parse the org buffer and then work with the resulting tree.
Thats the obvious thing to do in this case, and you can do everything
you want this way, but there are some alternatives too.
> But your exampl
Thanks a lot for the examples, they are very helpful! I first thought to
parse the org buffer and then work with the resulting tree. But your
examples now makes me think to work directly on the buffer. Well, I will
play with a few different ways now…
Regards
Eike
Thorsten Jolitz writes:
> Eike
Eike writes:
Hello,
> I want to ask for help regarding elisp and org-elements. I like to
> access the properties of all my headlines and I created the following
> function (tree is the parsed tree) that collects them into an a-list:
>
> #+begin_src emacs-lisp
> (defun collect-props (tree)
>
Hello again
it seems that I messed up my testing variables… I always had just one
headline and thus the list of lists had always one element that I then
extracted with `car'. So `car' must be removed:
#+begin_src emacs-lisp
(defun collect-props (tree)
(org-element-map tree 'headline
