From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: (Maybe) enhance `org-element-src-block-interpreter'?
Date: Wed, 06 Aug 2014 16:15:41 +0200 [thread overview]
Message-ID: <87oavx7lgy.fsf@gmail.com> (raw)
In-Reply-To: 87wqalztmj.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> I see, thanks. I'm still getting used to the 'org-element API', but it
>> seems to be much easier than I thought: just use
>> org-element-at-point' and
>> `org-element-interpret-data' in most cases ...
>
> Correct.
>
> For completeness, if you're working at the local level (i.e. with
> `org-element-at-point'), available accessors are
>
> - `org-element-type'
> - `org-element-property'
>
> When you're working at the global level (i.e. with
> `org-element-parse-buffer'), you get another accessor,
> `org-element-contents', and some tools to modify the parse tree
>
> - `org-element-put-property'
> - `org-element-adopt-element'
> - `org-element-insert-before'
> - `org-element-extract-element'
> - `org-element-set-element'
>
> In both cases, `org-element-interpret-data' is the only way to turn data
> back into Org syntax.
That makes things much clearer, thanks.
I definitely would have used `org-element-put-property' to modify a
'local' parse-tree too, but I can just as well directly use `plist-put'
on the raw plist in its cdr - would that be the correct way?
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-08-06 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 16:17 (Maybe) enhance `org-element-src-block-interpreter'? Thorsten Jolitz
2014-08-06 3:39 ` Aaron Ecay
2014-08-06 8:19 ` Thorsten Jolitz
2014-08-06 11:34 ` Nicolas Goaziou
2014-08-06 12:03 ` Thorsten Jolitz
2014-08-06 12:32 ` Nicolas Goaziou
2014-08-06 13:18 ` Nicolas Goaziou
2014-08-08 8:19 ` Thorsten Jolitz
2014-08-08 8:45 ` Nicolas Goaziou
2014-08-06 14:15 ` Thorsten Jolitz [this message]
2014-08-06 14:36 ` Thorsten Jolitz
2014-08-07 12:14 ` 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=87oavx7lgy.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).