From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: :header-args: over several lines?
Date: Mon, 07 Jul 2014 02:01:09 +0200 [thread overview]
Message-ID: <87bnt2t4u2.fsf@gmail.com> (raw)
In-Reply-To: m2mwczj1ck.fsf@krugs.de
Rainer M Krug <Rainer@krugs.de> writes:
> Along the same lines:
>
> When I use
>
> ,----
> | :header-args: :var RNGKIND="Mersenne-Twister"
> | :header-args+: :var RNGNORMALKIND="Inversion"
> `----
>
> both variables are transferred - is var+ generally redundant, or i=only
> in this case?
When I start using :var+ or :header-args+, it mostly does not work for me.
What is the syntax for this? Why and how is this used?
* Test
** Works 1
:PROPERTIES:
:header-args: :var x=3
:header-args+: :var y=4
:END:
#+begin_src emacs-lisp
(+ x y)
#+end_src
#+results:
: 7
(but does not work when variables reference other src_blocks, see my
bug report about :header-args:)
** Works 2
#+begin_src emacs-lisp :var u=2 v=3
(+ u v)
#+end_src
#+results:
: 5
** Works 3
#+header: :var u=2
#+header: :var v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
#+results:
: 5
#+headers: :var u=2
#+headers: :var v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
#+results:
: 5
** Does not work
#+header-args: :var u=2
#+header-args+: :var v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
=> progn: Symbol's value as variable is void: u
#+header-args: :var u=2
#+header-args+: :var+ v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
=> progn: Symbol's value as variable is void: u
#+var: u=2
#+var+: v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
=> progn: Symbol's value as variable is void: u
#+var: u=2 v=3
#+begin_src emacs-lisp
(+ u v)
#+end_src
=> progn: Symbol's value as variable is void: u
#+begin_src emacs-lisp :var u=2 :var+ v=3
(+ u v)
#+end_src
=> progn: Symbol's value as variable is void: v
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-07-07 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 21:05 :header-args: over several lines? Rainer M Krug
2014-06-26 0:01 ` Aaron Ecay
2014-06-26 12:34 ` Rainer M Krug
2014-07-07 0:01 ` Thorsten Jolitz [this message]
2014-07-27 23:05 ` Bastien
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=87bnt2t4u2.fsf@gmail.com \
--to=tjolitz@gmail.com \
--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).