From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Matt <matt@excalamus.com>, emacs-orgmode@gnu.org
Subject: Re: ob-shell sessions will send final echo '...' as input key sequence when previous command reads input interactively
Date: Wed, 03 May 2023 19:01:18 +0800 [thread overview]
Message-ID: <m2a5ylpt6d.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <878re5g0ir.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 4075 bytes --]
Ihor Radchenko <yantar92@posteo.net> writes:
> Matt <matt@excalamus.com> writes:
>
>> > Matt, maybe you have some ideas about this edge case?
>>
>> I have no other ideas within the current ob-shell implementation. As for modifications, I have the following thoughts.
>>
>> First, how might we state the problem for this edge case?
>>
>> To me, it looks like, "How can the ob-shell :async option manage interactive input?" Do you agree
>> with this formulation? If not, how do you see it differently?
>
> It is not about :async per se. Rather about using :session.
>
> A simple reproducer is
>
> #+begin_src bash :session test
> mpv "/path/to/some/video"
> m_
> #+end_src
>
> Basically, when you send multiline command in comint buffer without
> waiting for each line to finish, the following line may be read by the
> running command if that command is interactive.
>
> It is similar to a situation when you run a normal terminal like
>
> $ mpv "..."
> <now type "m_" while mpv is still running>
> <exit mpv>
> $ m_ <m_ is echoed in the next prompt>
>
Indeed, this explaination give me more clear understanding of the problem.
So currently ob-shell.el is async sending command into session buffer
without waiting for command to be finished.
I checked out the ob-shell.el source code. I suppose this is the core
part of the problem. From intuitive view, session async evaluation
indeed should not wait for command to be finished. But still feel a
little weird.
#+begin_src emacs-lisp
(session ; session evaluation
(if async
(progn
(let ((uuid (org-id-uuid)))
(org-babel-comint-async-register
session
(current-buffer)
"ob_comint_async_shell_\\(.+\\)_\\(.+\\)"
'ob-shell-async-chunk-callback
nil)
(org-babel-comint-async-delete-dangling-and-eval
session
(insert (format ob-shell-async-indicator "start" uuid))
(comint-send-input nil t)
(insert (org-trim body))
(comint-send-input nil t)
(insert (format ob-shell-async-indicator "end" uuid))
(comint-send-input nil t))
uuid))
(mapconcat
#'org-babel-sh-strip-weird-long-prompt
(mapcar
#'org-trim
(butlast ; Remove eoe indicator
(org-babel-comint-with-output
(session org-babel-sh-eoe-output t body)
(insert (org-trim body) "\n"
org-babel-sh-eoe-indicator)
(comint-send-input nil t))
;; Remove `org-babel-sh-eoe-indicator' output line.
1))
"\n")))
#+end_src
>> One thought is to update :async to work with the :stdin option so that
>> the block is run as a script. Currently, :stdin runs synchronously in
>> a separate shell. We might be able to grab the script's output and put
>> it into the session buffer. See how the following runs in a temporary
>> shell, regardless of the :session/:async options.
>
> Avoiding session altogether will indeed solve the problem, as :session
> is the place where the problem lies.
>
> Adding :stdin support is also an interesting idea, even out of scope of
> this discussion.
If this :stdin interesting idea works, maybe other similar ideas will too.🙋
For examples:
- Wrap command "mpv" with a shell function which disable accepting interactive input.
- Setting shell or environment variable in :prolog for source block to preventing interactive input.
Anyway, glad to get more interesting ideas.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.
Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2023-05-03 11:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 4:27 [Need Help] Error to evaluate "mpv" command in inline src block stardiviner
2023-04-30 4:46 ` Ruijie Yu via General discussions about Org-mode.
2023-04-30 10:59 ` Christopher M. Miles
2023-04-30 14:52 ` Ihor Radchenko
2023-05-01 3:39 ` Christopher M. Miles
2023-05-01 7:45 ` Ihor Radchenko
2023-05-01 10:46 ` Christopher M. Miles
2023-05-01 11:39 ` ob-shell sessions will send final echo '...' as input key sequence when previous command reads input interactively (was: [Need Help] Error to evaluate "mpv" command in inline src block) Ihor Radchenko
2023-05-01 12:50 ` ob-shell sessions will send final echo '...' as input key sequence when previous command reads input interactively Christopher M. Miles
2023-05-01 13:14 ` Ihor Radchenko
2023-05-01 13:41 ` Christopher M. Miles
2023-05-01 14:20 ` Ihor Radchenko
2023-05-01 19:06 ` Christopher M. Miles
2023-05-01 13:08 ` [SOLUTION] a temporary workaround solution using another language like "python" Christopher M. Miles
[not found] ` <35881.2693202466$1682946783@news.gmane.org>
2023-05-01 13:35 ` Max Nikulin
2023-05-01 19:01 ` Christopher M. Miles
2023-05-01 19:16 ` Ihor Radchenko
2023-05-02 4:17 ` [CLOSED] [ANSWER] " Christopher M. Miles
2023-05-02 20:31 ` ob-shell sessions will send final echo '...' as input key sequence when previous command reads input interactively (was: [Need Help] Error to evaluate "mpv" command in inline src block) Matt
2023-05-03 10:41 ` Ihor Radchenko
2023-05-03 11:01 ` Christopher M. Miles [this message]
2023-05-03 12:01 ` ob-shell sessions will send final echo '...' as input key sequence when previous command reads input interactively Ihor Radchenko
2023-05-03 16:31 ` Christopher M. Miles
2023-05-01 10:50 ` [Need Help] Error to evaluate "mpv" command in inline src block Christopher M. Miles
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=m2a5ylpt6d.fsf@numbchild@gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=matt@excalamus.com \
--cc=yantar92@posteo.net \
/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).