emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Local variables in an org file
Date: Thu, 20 Aug 2015 21:23:59 -0500	[thread overview]
Message-ID: <CAAjq1meoBzsTQxUw5g1o4rbn-WGnw0oWwY-OdHU-mzbGbRJLcA@mail.gmail.com> (raw)
In-Reply-To: <87fv3e4g63.fsf@iki.fi>

I've been thinking about this all week. Must be in the global memory space.
Grant Rettke
--
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
“All creativity is an extended form of a joke.” --Kay
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson


On Thu, Aug 20, 2015 at 1:39 AM, Jarmo Hurri <jarmo.hurri@iki.fi> wrote:
>
> Greetings.
>
> Is there a way to define a (preferably local) variable in an org file so
> that the value of that variable could be referenced in both plain text
> and code blocks?
>
> I often bump into situations where I have a value, say 768, and I use
> that value both in code blocks and in the accompanying text. Now basic
> programming approach tells me that if and when I need to change that
> value, I should be able to do that by changing the value in only one
> location. That implies defining a variable for the value.
>
> Properties sound like they might be the solution. But I don't know how
> to refer to properties in text and code.
>
> Jarmo
>
>

  reply	other threads:[~2015-08-21  2:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  6:39 Local variables in an org file Jarmo Hurri
2015-08-21  2:23 ` Grant Rettke [this message]
2015-08-21  2:52   ` Thomas S. Dye
2015-08-21 10:54     ` Jarmo Hurri
2015-08-21 11:57       ` Rainer M Krug
2015-08-21 17:08       ` Thomas S. Dye

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=CAAjq1meoBzsTQxUw5g1o4rbn-WGnw0oWwY-OdHU-mzbGbRJLcA@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@iki.fi \
    /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).