emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Wed, 6 Jul 2016 10:36:55 -0700	[thread overview]
Message-ID: <alpine.OSX.2.20.1607061017580.581@charles-berrys-macbook.local> (raw)
In-Reply-To: <COL125-W27B126B39005909AD688D5EB3A0@phx.gbl>

On Tue, 5 Jul 2016, Joon Ro wrote:

> Hi,

> I'm aware of passing variables through header arguments, and also 
> inserting another source code block using the noweb syntax.

> I was wondering, however, would it be possible to directly input values 
> of properties inside source code blocks? For example,

Yes. `org-property-values' does the trick


* Subtree
:PROPERTIES:
:DUMMY: Value
:END:

#+BEGIN_SRC shell :var dumdum=(car (org-property-values "DUMMY"))
echo $dumdum
#+END_SRC

#+RESULTS:
: Value

#+NAME: get-property
#+BEGIN_SRC emacs-lisp :var prop="prop"
(org-property-values prop)
#+END_SRC

#+BEGIN_SRC emacs-lisp :noweb yes
(quote
<<get-property(prop="DUMMY")>>
)
#+END_SRC

#+RESULTS:
| Value |

HTH,

Chuck

  reply	other threads:[~2016-07-06 17:37 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 [this message]
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
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.1607061017580.581@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).