emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Alekseyev <dnquark@gmail.com>
To: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Blank first line in a tangled file prevents src block execution
Date: Fri, 9 Mar 2012 16:57:10 -0500	[thread overview]
Message-ID: <CADzxs1mAEj+U5LvFUJHc7sRw618aXALGvano_zA5rdHpobX8Xw@mail.gmail.com> (raw)

I have the following source block that I tangle to produce a short script:

#+begin_src sh :tangle code/get_wavs.sh
  #!/bin/bash
  for fn_in in "$@"; do
      fn_out=$(sed -e 's|\.3gp$||g' -e 's|$|.wav|g' <<< $fn_in)
      ffmpeg -i $fn_in -vn -f wav -acodec pcm_u8 $fn_out
  done
#+end_src

However, the tangled file has a blank first line.  As a result, I
can't seem to run this script either using sh -c, or by putting it
inside a code block.  In other words, the following line fails:

sh -c "code/test.sh data/salsa/20120308_av_jc/song2/*.3gp"
code/test.sh: 4: Syntax error: redirection unexpected

And, similarly, this fails

#+begin_src sh
  code/get_wavs.sh data/salsa/20120308_av_jc/song2/*.3gp
#+end_src


On the other hand, the script runs fine from the command line, or from
an org-mode shell: link, i.e. just running

code/test.sh data/salsa/20120308_av_jc/song2/*.3gp

at bash prompt produces the desired result.


I am not sure what the rules are about blank lines before the
hash-bang directive in Bash, and why in particular the blank line
seems to cause sh -c ... and orb-babel src execution to break, but the
current behavior seems broken.

             reply	other threads:[~2012-03-09 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 21:57 Leo Alekseyev [this message]
2012-03-09 22:08 ` Blank first line in a tangled file prevents src block execution Nick Dokos
2012-03-09 22:26   ` Eric Schulte
2012-03-09 23:14     ` Nick Dokos
2012-03-12  4:40       ` Eric Schulte

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=CADzxs1mAEj+U5LvFUJHc7sRw618aXALGvano_zA5rdHpobX8Xw@mail.gmail.com \
    --to=dnquark@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).