From: Eric Schulte <eric.schulte@gmx.com>
To: Tom Regner <tom@goochesa.de>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
Panruo Wu <pwu@mymail.mines.edu>
Subject: Re: org babel execute shell in sh?
Date: Mon, 12 Mar 2012 13:29:02 -0400 [thread overview]
Message-ID: <87aa3ld8yp.fsf@gmx.com> (raw)
In-Reply-To: 874ntt6ah1.fsf@goochesa.de
Tom Regner <tom@goochesa.de> writes:
> Eric Schulte <eric.schulte@gmx.com> writes:
>
>>>
>>> But I'm often bitten by the distinction between export and tangling --
>>> :padline, :shebang come to mind, where I expected org-babel to honour
>>> the setting in both cases.
>>>
>>
>> Could you describe a use case where these options would be used for
>> exporting and would be preferable to simply including the padding lines
>> or the shebang literally in the code block?
>
> I use an LP org-document with zsh-codefragments to generate a CLIF
> testplan - the script is tangled, then executed and the output -- the
> generated .ctp file -- exported. In this case I'd prefere it to have the
> shell from the :shebang option used to run the tangled program, not
> /bin/sh, so that exporting the output inside the document and running
> the tangled program standalone produce the same result.
>
> At the moment I have to set the shell document- or session-wide to zsh
> to get reproducible behaviour.
>
> Whenever the export/execution is part of the generated document and of
> the generated product (the tangled code) I would like it, not to have to
> sides to configure.
>
> I don't know, if I make myself clear -- If not, please tell me so and I
> try to distill an example out of the cases I encountered at work, where
> I was wondering why some things did not work as I expected.
>
I think I understand now, so it is "execution" not "export" behavior
which could make use of the :shebang header argument. I suppose that it
would be possible to allow the :shebang header argument to silently
override the value of the `org-babel-sh-command' variable when it is
present.
I just pushed up a patch which adds this behavior. It does result in
some odd new possibilities, such as the following.
#+begin_src sh :shebang #!/bin/cat
foo
#+end_src
#+RESULTS:
| #!/bin/cat |
| |
| foo |
Best,
>
> Kind regards,
> Tom
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-03-12 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 17:25 org babel execute shell in sh? Panruo Wu
2012-03-08 0:22 ` Nick Dokos
2012-03-08 4:24 ` Tom Regner
2012-03-09 20:34 ` Panruo Wu
2012-03-10 4:21 ` Nick Dokos
2012-03-10 6:33 ` Tom Regner
2012-03-12 4:34 ` Eric Schulte
2012-03-12 16:38 ` Tom Regner
2012-03-12 17:29 ` Eric Schulte [this message]
2012-03-12 19:10 ` Nick Dokos
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=87aa3ld8yp.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=pwu@mymail.mines.edu \
--cc=tom@goochesa.de \
/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).