emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Loris Bennett <loris.bennett@fu-berlin.de>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Sharing variables between source blocks without session
Date: Fri, 19 Mar 2021 07:38:47 +0100	[thread overview]
Message-ID: <87h7l7ps08.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <MW3PR20MB341781447D4C63AADA354488BE699@MW3PR20MB3417.namprd20.prod.outlook.com> (Malcolm Cook's message of "Thu, 18 Mar 2021 17:59:48 +0000")

"Cook, Malcolm" <MEC@stowers.org> writes:

> Eric S Fraga <mailto:e.fraga@ucl.ac.uk> writes:
>>> On Tuesday, 16 Mar 2021 at 09:56, Loris Bennett wrote:
>>>> How can I avoid having to declare the variable 'user' for both blocks?
>>> I imagine you could use a property, as in
>>> #+property: header-args :var user=loris
>>> or even make it specific for the particular language.
>>> (untested)
>>Thanks for point out using 'header-args;' as property. However, if I do
>>the following, the variable is unset in the shell script:
>>#+properties: header-args :var user=loris
>>#+begin_src sh
>>echo user: ${user}
>>: user:
>>Is that supposed to work, or am I doing something wrong?
> I am unfamiliar with using the plural form of property, as you are trying, at buffer-level nor do I see  documented possible here:
> https://orgmode.org/manual/Property-Syntax.html#Property-Syntax
> try this:
> #+property: header-args:sh :var user="loris"
> #+begin_src sh
> echo user: ${user}
> #+end_src
> Important: After adding or modifying the #+property line, you will need to instruct org to "refresh your local setup" which I typically accomplish by positioning the point on that line and typing C-c C-c

This doesn't work for me - there is no error, but I get the same result
as above, i.e. the variable ${users} is not set.  Does it work for you?  

What does work for me is using a section property rather than a buffer

* Dummy Section
  :header-args: :R :var user="loris"

#+begin_src sh
  echo user: ${user}

: user: loris

However, the restriction to source blocks of a particular language does
not seem to work like this, but maybe I have got the syntax wrong

>>This signature is currently under construction.

  reply	other threads:[~2021-03-19  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  8:56 Sharing variables between source blocks without session Loris Bennett
2021-03-16  9:16 ` Loris Bennett
2021-03-16 13:28 ` Eric S Fraga
2021-03-18 13:21   ` Loris Bennett
2021-03-18 15:56     ` Eric S Fraga
2021-03-19  6:50       ` Loris Bennett
2021-03-18 17:59     ` Cook, Malcolm
2021-03-19  6:38       ` Loris Bennett [this message]
2021-03-19  7:04         ` Loris Bennett
2021-03-19 13:26         ` Eric S Fraga
2021-03-19 13:59           ` Loris Bennett
2021-03-19 14:26             ` Eric S Fraga
2021-03-22  7:39               ` Loris Bennett

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:

  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=87h7l7ps08.fsf@hornfels.zedat.fu-berlin.de \
    --to=loris.bennett@fu-berlin.de \
    --cc=emacs-orgmode@gnu.org \


* 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).