From: Joon Ro <joon.ro@outlook.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Using property values in source code blocks
Date: Wed, 6 Jul 2016 22:50:46 -0500 [thread overview]
Message-ID: <COL125-W237D80C5C05CED0F172044EB3B0@phx.gbl> (raw)
In-Reply-To: <alpine.OSX.2.20.1607061600580.479@charles-berrys-macbook.local>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
> I have no idea what you are asking.
>
> > The reason is I have to put those values inside a comment,
> > so I cannot pass them as variables.
>
> So your original query about accessing property values from src blocks was
> not what you wanted?
>
> Examples of what one is trying to do - even if they do not work exactly as
> intended - are often more helpful than verbal explanations of what one
> would like to do.
>
> Chuck
>
I'm sorry if my explanation was not clear, but the original example I provided shows exactly what I wanted to do:
* Subtree:PROPERTIES::DUMMY: VALUE:END:#+BEGIN_SRC{{DUMMY}} <- something like this?#+END_SRC
Basically, I want to replace {{DUMMY}} with VALUE, without passing it as a variable. So just like <<noweb>> replacement, but with a property value instead of a code block. I get the feeling that this is not possible, but I wanted to ask just in case.
Best,Joon
[-- Attachment #2: Type: text/html, Size: 3649 bytes --]
next prev parent reply other threads:[~2016-07-07 3:50 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 [this message]
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=COL125-W237D80C5C05CED0F172044EB3B0@phx.gbl \
--to=joon.ro@outlook.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
/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).