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: Sat, 16 Jul 2016 09:02:35 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1607160829390.570@charles-berrys-macbook.local> (raw)
In-Reply-To: <COL125-W7A378CE5C5EFA0A2CF99CEB340@phx.gbl>
On Fri, 15 Jul 2016, Joon Ro wrote:
>
>
>>
>> Example:
>>
>> --8<---------------cut here---------------start------------->8---
>>
>> * Top Heading
>>
>> #+NAME: get-property
>> #+BEGIN_SRC emacs-lisp :noweb yes :var prop="prop" :var pom=0
>> (car (org-entry-get-multivalued-property pom prop))
>> #+END_SRC
>>
>> ** Subheading
>> :PROPERTIES:
>> :DUMMY: 100
>> :END:
>>
>> #+BEGIN_SRC shell :noweb yes
>> echo <<get-property(prop="DUMMY",pom=(point))>>
>> #+END_SRC
>>
>> #+RESULTS:
>> : 100
>>
>> --8<---------------cut here---------------end--------------->8---
>>
>
> Hi Chuck,
> Thank you so much. It definitely works when I evaluate the code block -
> but my ultimate goal is to tangle the source code (I want to generate
> bunch of script files with a template using property values), and when I
> tangle the code block it returns nil.
I do not see an easy way to do what you want only with tangle.
There are hooks you can define that might enable you to set things up.
Maybe you can use `org-babel-pre-tangle-hook' to collect the property
values and put them somewhere that `org-babel-post-tangle-hook' can get at
them and use them to modify the tangled results accordingly. Or maybe
`org-babel-post-tangle-hook' can do it by using methods like those in
`org-babel-detangle' to look back at the *.org file.
Another alternative is to write all of your code blocks so they will
execute to create the code you want as results and then tangle those
results. You would use :wrap like this:
--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC shell :noweb yes :wrap "src shell :tangle ./tangle-test.sh"
echo "echo " <<get-property(prop="DUMMY",pom=(point))>>
#+END_SRC
--8<---------------cut here---------------end--------------->8---
Execute the src block and then tangle the buffer.
In fact, if you go that route it might make more sense to write elisp
code blocks to find the prpoerty values and then format the results.
Chuck
next prev parent reply other threads:[~2016-07-16 16:02 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
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 [this message]
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.1607160829390.570@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).