emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Victor A. Stoichita" <victor@svictor.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: passing variables to lilypond code blocks
Date: Thu, 18 Feb 2021 12:42:45 +0100	[thread overview]
Message-ID: <87lfbld2kq.fsf@svictor.net> (raw)

I’m trying to understand how ob-lilypond handles variables.
I have the following minimal example which compiles correctly:
#+begin_src lilypond :file test.png :cache no
  myVar = { e f g}
  \relative c' { a b c d \myVar }

Can I move the definition of myVar to a header argument of the 
source block?
When I write this: 
#+begin_src lilypond :file test.png :cache no :var 
 myVar="{ e f g }"
  \relative c' { a b c d \myVar }
The compiler complains: "unknown escaped string: `\myVar'".

This makes me think that myVar is not passed at all to the code 
block. What is the correct way to do this?

I know that I can do it with noweb syntax. However, I would prefer 
to use header args because I need those variables in all lilypond 
code blocks. Ultimately, I plan to pass them from 


                 reply	other threads:[~2021-02-18 11:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87lfbld2kq.fsf@svictor.net \
    --to=victor@svictor.net \
    --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).