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
Matt writes:
> Changing the `ob-shell-async-chunk-callback' like this will fix it:
>
> @@ -276,7 +276,7 @@ See `org-babel-comint-async-indicator'.")
> (defun ob-shell-async-chunk-callback (string)
>"Filter applied to results before insertion.
> See `org-babel-comint-async-chunk-callback'."
> 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
On Thu, 23 Mar 2023 07:12:29 -0400 Christopher M. Miles wrote ---
> #+begin_src bash :session "*ob-shell-bash*" :async t
> sleep 30
> echo "hello, world"
> #+end_src
>
> #+RESULTS[(2023-03-23 19:14:15) 23f9ad130f7a1268e21821c6baaea2b057c70d3e]:
> : org_babel_sh_prompt> hello, w
Matt writes:
> On Wed, 22 Mar 2023 23:25:50 -0400 Christopher M. Miles wrote ---
> >
> > The ob-shell async result output contains the shell prompt. I think it
> > should not be captured.
> >
> > #+begin_src shell :session "test2" :async t
> > sleep 30
> > echo "hello, world"
>
On Wed, 22 Mar 2023 23:25:50 -0400 Christopher M. Miles wrote ---
>
> The ob-shell async result output contains the shell prompt. I think it
> should not be captured.
>
> #+begin_src shell :session "test2" :async t
> sleep 30
> echo "hello, world"
> #+end_src
>
> #+RESULTS[(
The ob-shell async result output contains the shell prompt. I think it
should not be captured.
#+begin_src shell :session "test2" :async t
sleep 30
echo "hello, world"
#+end_src
#+RESULTS[(2023-03-23 11:19:22) 461ed5de684f6e619890709175ec73e80b67b2d6]:
: bash-5.2$ hello, world
--
[ stardivine
10 matches
Mail list logo
