From: Aaron Ecay <aaronecay@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: (Maybe) enhance `org-element-src-block-interpreter'?
Date: Tue, 05 Aug 2014 23:39:23 -0400 [thread overview]
Message-ID: <87oavywal0.fsf@gmail.com> (raw)
In-Reply-To: <87tx5qvrl4.fsf@gmail.com>
Hi Thorsten,
2014ko abuztuak 5an, Thorsten Jolitz-ek idatzi zuen:
[...]
>
> Parse this src-block (with point at beg of block):
>
> ,----
> | M-: (setq ptree (org-element-at-point))
> `----
>
> #+header: :results raw
> #+begin_src emacs-lisp
> (message "hello world")
> #+end_src
>
> #+results:
> hello world
>
> Then evaluate
>
> #+begin_src emacs-lisp
> (org-element-src-block-interpreter ptree nil)
> #+end_src
>
> #+results:
> : #+BEGIN_SRC emacs-lisp
> : (message "hello world")
> : #+END_SRC
>
> #+begin_src emacs-lisp
> (tj/src-block-interpreter ptree nil)
> #+end_src
>
> #+results:
> : #+HEADER: :results raw
> : #+BEGIN_SRC emacs-lisp
> : (message "hello world")
> : #+END_SRC
Indeed this seems like an improvement on the status quo. But other
elements of org syntax (not just src blocks) can have a valid #+header
(and indeed other affiliated keywords, like #+attr_latex), so the fix
probably should be more general.
--
Aaron Ecay
next prev parent reply other threads:[~2014-08-06 3:39 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 [this message]
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
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=87oavywal0.fsf@gmail.com \
--to=aaronecay@gmail.com \
--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).