emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Gauland <mikelygee@gmail.com>
To: emacs-orgmode@gnu.org
Subject: header-args property
Date: Thu, 1 Apr 2021 21:23:05 +1300	[thread overview]
Message-ID: <41610a78-cc6c-48b3-9049-6d8f9d61f14e@gmail.com> (raw)

I'm confused about the use of the header-args property. It works as
expected when I
export a file, but not when I evaluate a code block manually. For example,
consider this file:

    #+PROPERTY: header-args :var x="Hello" :exports both

    #+begin_src shell
      echo X is $x

When I export, the result of the code block is "X is Hello", but when I
use C-c
C-c to evaluate the block in emacs, I get "X is"--the variable isn't

In practice, this means I generally define things like :session for each
rather than using a file-level property. Is this behaviour expected? 

Kind regards,


             reply	other threads:[~2021-04-01  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  8:23 Michael Gauland [this message]
2021-04-01 11:04 ` header-args property Greg Minshall
2021-04-01 11:10 ` ian martins
2021-04-01 11:47 ` Eric S Fraga

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=41610a78-cc6c-48b3-9049-6d8f9d61f14e@gmail.com \
    --to=mikelygee@gmail.com \
    --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).