emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Trouble passing variables into shell blocks on windows
Date: Tue, 23 Jun 2015 10:50:44 +0200	[thread overview]
Message-ID: <86k2uubyfv.fsf@example.com> (raw)
In-Reply-To: CAC5XeFExrfh3EuRbBRkO3J-4e=na1urCkmDekdgVS79=skfHyA@mail.gmail.com

Johan W. Klüwer <johan.w.kluwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thank you for the information -- I suppose the cygwin version of emacs may
> be the only viable option. Still that seems like quite a big change,
> swapping emacs versions, just for this particular feature.
>
> 2015-06-15 10:12 GMT+02:00 Rainer M Krug <Rainer-vfylz/Ys1k4@public.gmane.org>:
>> Johan W. Klüwer <johan.w.kluwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>> I'm having difficulties passing org variables into shell source blocks.
>>> This is using Windows 7 and Cygwin with bash shell. For instance, the
>>> following
>>>
>>> #+BEGIN_SRC sh :var x="."
>>>   ls $x
>>> #+END_SRC
>>>
>>> fails with the error message (as displayed in emacs)

I dunno what's the real impact of that, but pay attention that the "sh"
language has been renamed "shell" quite a long time ago (more than one
year IIRC).

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2015-06-23  8:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 13:13 Trouble passing variables into shell blocks on windows Johan W. Klüwer
2015-06-15  8:12 ` Rainer M Krug
2015-06-23  7:28   ` Johan W. Klüwer
2015-06-23  8:50     ` Sebastien Vauban [this message]
2015-06-16 13:28 ` Andy Moreton

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=86k2uubyfv.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).