From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Somelauw ." <somelauw@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Add contents-begin and contents-end to src-block in org-element.el
Date: Mon, 25 Dec 2017 09:49:00 +0100 [thread overview]
Message-ID: <87o9mnfb0j.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CA+gt_a-NOx1u1+L8q8Y3QjTfd7SWJ_awjmtUcYtnT3_qnD6bUA@mail.gmail.com> (Somelauw .'s message of "Mon, 25 Dec 2017 00:55:45 +0100")
Hello,
"Somelauw ." <somelauw@gmail.com> writes:
> 2017-12-24 16:05 GMT+01:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
>> Contents mean "data in Org syntax". There are no such contents in source
>> blocks. Therefore, the parser does not provide :contents-begin
>> and :contents-end for them.
>
> Thanks for your quick response As I understand from your reply,
> :contents-begin/end should be reserved for elements that can contain
> other org-elements or org-objects.
>
> I'm writing a plugin that allows one to operate on the inner body of
> an org-element and so far I'm relying on :contents-begin and
> :contents-end. This has worked pretty well so far on most org
> elements, but org-src-blocks seem to be an exception. I may want to
> special-case these.
>
> By the way, do you know of any other org-elements that have an inner
> body that doesn't classify as "data in Org syntax"?
comment, comment blocks, example blocks, export blocks, fixed-width,
keyword, latex-environment, node property.
These elements usually set :value property instead.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-12-25 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 14:56 Add contents-begin and contents-end to src-block in org-element.el Somelauw .
2017-12-24 15:05 ` Nicolas Goaziou
2017-12-24 23:55 ` Somelauw .
2017-12-25 8:49 ` Nicolas Goaziou [this message]
2017-12-25 13:09 ` Somelauw .
2017-12-25 22:42 ` Nicolas Goaziou
2017-12-27 20:50 ` Somelauw .
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=87o9mnfb0j.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=somelauw@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).