From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Joon Ro <joon.ro@outlook.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Using property values in source code blocks
Date: Thu, 7 Jul 2016 08:48:03 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1607070838510.537@charles-berrys-macbook.local> (raw)
In-Reply-To: <COL125-W237D80C5C05CED0F172044EB3B0@phx.gbl>
On Wed, 6 Jul 2016, Joon Ro wrote:
>
>
>
>> I have no idea what you are asking.
>>
[snip]
> I'm sorry if my explanation was not clear, but the original example I
> provided shows exactly what I wanted to do:
And my response showed how to do it: you construct a src block with a
noweb reference that places the *results* of evaluating another src block
in the code (or comment). The src block in the named in the noweb
reference handles retrieving the property value, viz.
--8<---------------cut here---------------end--------------->8---
* Subtree
:PROPERTIES:
:DUMMY: Value
:END:
#+NAME: get-property
#+BEGIN_SRC emacs-lisp :var prop="prop"
(car (org-property-values prop))
#+END_SRC
#+BEGIN_SRC shell :noweb yes
echo <<get-property(prop="DUMMY")>>
#+END_SRC
#+RESULTS:
: Value
--8<---------------cut here---------------end--------------->8---
See
(info "(org) Noweb reference syntax")
Chuck
next prev parent reply other threads:[~2016-07-07 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 4:10 Using property values in source code blocks Joon Ro
2016-07-06 17:36 ` Charles C. Berry
2016-07-06 20:03 ` Joon Ro
2016-07-06 23:05 ` Charles C. Berry
2016-07-07 3:50 ` Joon Ro
2016-07-07 15:48 ` Charles C. Berry [this message]
2016-07-07 15:53 ` Joon Ro
2016-07-15 23:38 ` Joon Ro
2016-07-15 23:44 ` Joon Ro
2016-07-16 2:05 ` Charles C. Berry
2016-07-16 2:47 ` Joon Ro
2016-07-16 16:02 ` Charles C. Berry
2016-07-16 17:00 ` Joon Ro
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=alpine.OSX.2.20.1607070838510.537@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=joon.ro@outlook.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).