Re: org babel execute shell in sh?

[Tom Regner <tom@goochesa.de>]

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.

Kind regards,
Tom