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 14:03:31 +0200 [thread overview]
Message-ID: <87wqal7rl8.fsf@gmail.com> (raw)
In-Reply-To: 87egwt26o3.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
Hello,
>> Yes, there are other elements and more affiliated keywords. The
>> parser (or rather the interpreter(s)) and parts of Org Babel do not
>> always deal with them yet.
>>
>> This was more a 'constructive bug report', not so much an attempt of a
>> general fix. I just (partly) fixed this function for myself because I
>> needed it ...
>
> There is no bug here.
>
> `org-element-src-block-interpreter' is meant to create a src block and
> only a src block. `org-element--interpret-affiliated-keyword' is used to
> create affiliated keywords (like "#+header"). You shouldn't call any of
> these anyway, since `org-element-interpret-data' is the one and only
> entry point to interpret parsed data. Try
>
>
> (org-element-interpret-data ptree)
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 ...
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-08-06 12:03 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 [this message]
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
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=87wqal7rl8.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).