From: Vitalie Spinu <spinuvit@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export: how to copy the parsed tree?
Date: Sat, 01 Mar 2014 13:21:26 -0800 [thread overview]
Message-ID: <877g8deht5.fsf@gmail.com> (raw)
In-Reply-To: <878ustpr7k.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 01 Mar 2014 22:02:55 +0100")
>>> Nicolas Goaziou on Sat, 01 Mar 2014 22:02:55 +0100 wrote:
[...]
> In this case, I think I would build the tree, since data is duplicated
> (e.g. "* H1"), not moved.
Is there an idiomatic way to do this? Like constructors of org elements?
Or, one just starts with an empty '(headline) list and populate it with
org-element-set-contents and org-element-put-property?
[...]
>> The :parent seems to be stored in 2 places for the headline, in the
>> headline itself and in the :title.
> You are wrong. Headline's parent is stored only in the :parent property
> of the headline. You get it with:
> (org-element-property :parent headline)
> Within `:title', `:parent' property refers to the parent of the objects
> contained in :title, which is the headline itself:
> (eq (org-element-property :parent
> ;; The first object in the :title property.
> (car (org-element-property :title headline)))
> headline) => t
It makes sense now. Thanks.
[...]
>> BTW, is there a way to pretty print the org tree? I think that's the
>> main barrier for me in understanding how it all works.
> Use `pp' and set both `print-level' and `print-circle' accordingly.
Thanks. Didn't know about this.
Vitalie
next prev parent reply other threads:[~2014-03-01 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 1:20 org-export: how to copy the parsed tree? Vitalie Spinu
2014-03-01 8:45 ` Thorsten Jolitz
2014-03-01 10:21 ` Thorsten Jolitz
2014-03-01 11:36 ` Nicolas Goaziou
2014-03-01 18:24 ` Vitalie Spinu
2014-03-01 21:02 ` Nicolas Goaziou
2014-03-01 21:21 ` Vitalie Spinu [this message]
2014-03-02 9:13 ` Nicolas Goaziou
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=877g8deht5.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).