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 14:59:19 +0100 [thread overview]
Message-ID: <87blbfnt1k.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <87mtuz9swb.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 19 Mar 2021 13:26:12 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Friday, 19 Mar 2021 at 07:38, Loris Bennett wrote:
>> 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
>> (again).
>
> Maybe ;-)
>
> This seems to work for me for a shell:
>
> :PROPERTIES:
> :header-args:sh: :var user="loris"
> :END:
That works for me, too. The following correctly does not work:
:PROPERTIES:
:header-args:R: :var user="loris"
:END:
#+begin_src sh
echo user ${user}
#+end_src
#+RESULTS:
: user
To be honest, I find it is a wee bit confusing that it's
#+PROPERTY: header-args:sh :var user="loris"
*without* a colon after the language (if I add it, there is not error,
but the variable is just not set) but
:PROPERTIES:
:header-args:sh: :var user="loris"
:END:
*with* a colon after the language, but maybe I'm just easily confused
:-)
Thanks for the help,
Loris
--
This signature is currently under construction.
next prev parent reply other threads:[~2021-03-19 14:01 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
2021-03-19 7:04 ` Loris Bennett
2021-03-19 13:26 ` Eric S Fraga
2021-03-19 13:59 ` Loris Bennett [this message]
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:
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=87blbfnt1k.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.de \
--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).