From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: (Maybe) enhance `org-element-src-block-interpreter'?
Date: Fri, 08 Aug 2014 10:45:23 +0200 [thread overview]
Message-ID: <87y4uzmkt8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r40rv1en.fsf@gmail.com> (Thorsten Jolitz's message of "Fri, 08 Aug 2014 10:19:44 +0200")
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Accessor `org-element-contents' is badly missed here ...
>
> E.g. I can get locally the content of a src-block (its :value), but for
> most other elements (e.g. paragraph) that is not true. OTOH I cannot
> reuse a src-block value as the content of a (locally created) paragraph
> because this element has no :value property I could set (and its
> interpreter simply inserts 'content', which is unaccessible on local
> level).
>
> I know this is *much* easier asked as provided:
> can getters and setters for element-content be introduced at the local
> level too?
No, `org-element-at-point' focuses on the element at point, not elements
within. It would slow it down and make caching more complicated, for
little benefit.
> maybe via another property shared by all elements (:content
> ?). The content is probably not even parsed at local level, but anyway,
> maybe there is some kind of trick to make it accessible without parsing
> the whole buffer?
>
> The only thing that comes to my mind is narrow the buffer to
> element-at-point and then parse only this visible buffer part and return
> its content. Valid idea?
You're correct. Some cleanup is needed though (org-data + section
elements).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-08-08 8:45 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 [this message]
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=87y4uzmkt8.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@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).