From: Johannes Rainer <johannes.rainer@i-med.ac.at>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: macro expansion in source code
Date: Thu, 29 Aug 2013 21:22:59 +0200 [thread overview]
Message-ID: <CABxYo6rukOVuSY8LO7+VktCJDPtbPn7gRuxMqfcQQiQg2_7tmg@mail.gmail.com> (raw)
In-Reply-To: <loom.20130829T170757-251@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
thanks for that solution! I will give it a try!
On Thu, Aug 29, 2013 at 5:15 PM, Charles Berry <ccberry@ucsd.edu> wrote:
> Johannes Rainer <johannes.rainer <at> gmail.com> writes:
>
> >
> >
> > hi,
> > I was just wondering if there is a way to use macro expansion also in
> > source code blocks or headers. I tried this, but the macro was never
> > expanded, but rather the {{{image_width}}} was exported. could the
> > expansion be done by calling the macro expansion before export
> > (e.g. using a hook)?
> >
> > something like this:
>
> [snip]
>
> I think the answer is no. But you can accomplish much the same thing with
> properties and/or noweb references. Like this
>
> * header
> :PROPERTIES:
> :image_width: 16
> :END:
>
> #+NAME: imwide
> #+HEADER: :var iw=(org-entry-get (point) "image_width")
> #+BEGIN_SRC R :results value
> iw
> #+END_SRC
>
> #+RESULTS: imwide
> : 16
>
>
> #+BEGIN_SRC R :noweb yes :results output
> image.width <-
> <<imwide()>>
> image.width
> #+END_SRC
>
> #+RESULTS:
> : [1] 16
>
>
>
>
>
--
Johannes Rainer, PhD
Applied Bioinformatics Group,
Division Molecular Pathophysiology,
Biocenter, Medical University Innsbruck,
Innrain 80/82 II, 6020 Innsbruck, Austria
and
Tyrolean Cancer Research Institute
Innrain 66, 6020 Innsbruck, Austria
Tel.: +43 (0)512 9003 70961
Email: johannes.rainer@i-med.ac.at
johannes.rainer@tcri.at
URL: http://bioinfo.i-med.ac.at
[-- Attachment #2: Type: text/html, Size: 2266 bytes --]
prev parent reply other threads:[~2013-08-29 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 11:52 macro expansion in source code Johannes Rainer
2013-08-29 15:15 ` Charles Berry
2013-08-29 19:22 ` Johannes Rainer [this message]
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=CABxYo6rukOVuSY8LO7+VktCJDPtbPn7gRuxMqfcQQiQg2_7tmg@mail.gmail.com \
--to=johannes.rainer@i-med.ac.at \
--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).