From: Rainer M Krug <email@example.com>
To: "Thomas S. Dye" <firstname.lastname@example.org>
Cc: emacs-orgmode <email@example.com>
Subject: Re: using variables in org text
Date: Sat, 18 Feb 2012 11:52:39 +0100 [thread overview]
Message-ID: <CAGhLh6GgDgxrBRfF5fmMsR5nszYpJk2zQVJwXuUP4nt4qMftrw@mail.gmail.com> (raw)
On 16 February 2012 17:05, Thomas S. Dye <firstname.lastname@example.org> wrote:
> Rainer M Krug <email@example.com> writes:
>> I have defined a variable as follow
>> #+property: var DC="/home/rkrug/tmp/CLUSTER"
>> and I am using this path quite often in source blocks (works nicely as
>> expected) but also in org directly, e.g.
>> * DC path is $DC$
>> The DC path $DC$ is pointing to a directory.
>> Is it possible to use the variable DC in the text as well, so that
>> $DC$ is replaced with the value of the variable DC as defined above?
>> In other words: how can I tell org that on export, $DC$ stands for the
>> value of the variable DC?
>> PS: I know that $...$ is for LaTeX math mode
> Aloha Rainer,
> Here is a way that works for me.
> * Krug
> How to have a variable show up in text.
> #+name: printDC
> #+BEGIN_SRC emacs-lisp :results silent raw :exports none
> (print DC)
> In the text call_printDC() is shown.
Great idea - I will try it as soon as I am back at work.
> Thomas S. Dye
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax (F): +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
prev parent reply other threads:[~2012-02-18 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 14:35 using variables in org text Rainer M Krug
2012-02-16 16:05 ` Thomas S. Dye
2012-02-18 10:52 ` Rainer M Krug [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).