On Fri, 24 Mar 2023 07:38:58 -0400 Ihor Radchenko wrote ---
> I suggest the following:
> 1. Introduce a new customization `org-babel-default-shell', defaulting
>to (or (executable-find "sh") (executable-find "cmd.exe")).
> 2. Use the value as default shell in "shell" code block
Samuel Wales writes:
> i have a vague memory of having used sh and then we were told to use
> shell. can we all use begin src sh now?
You can use anything listed in `org-babel-shell-names'.
Also, see https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html
--
Ihor Radchenko // y
i have a vague memory of having used sh and then we were told to use
shell. can we all use begin src sh now?
On 3/24/23, Ihor Radchenko wrote:
> Matt writes:
>
>> What benefit does "shell" provide?
>>
>> - The "shell" language allows an arbitrary executable to be run. This
>> means that shells
Matt writes:
> What benefit does "shell" provide?
>
> - The "shell" language allows an arbitrary executable to be run. This means
> that shells other than those given in `org-babel-shell-names' can be run.
> People using a non-supported shell could still benefit from ob-shell.
>
> What downsi
At first, thanks for this long parsing and explanation.
Matt writes:
> > Matt m...@excalamus.com> writes:
> >
> > > Is there a reason you're using "shell" instead of one of the shells
> listed in `org-babel-shell-names'?
>
> I'm still curious why you're using "shell". I want to know if it'
> Matt m...@excalamus.com> writes:
>
> > Is there a reason you're using "shell" instead of one of the shells listed
> > in `org-babel-shell-names'?
I'm still curious why you're using "shell". I want to know if it's something
you're using for a specific reason. There's no wrong answer!
I a
