Re: bash source code block: problem after ssh commands

[Ihor Radchenko <yantar92@posteo.net>]

Max Nikulin <manikulin@gmail.com> writes:

> ... ob-shell might offer variants for sessions: dumb 
> stdin, source a temporary file, or bracketed paste. Anything besides 
> stdin (with its confusing differences from interactive sessions) is 
> almost certainly requires shell-specific code. And `shell' is likely not 
> suitable with its TERM=dumb.

We use comint buffers for sessions. Nothing else.
It is non-session blocks that have variants of how they are evaluated.

And, since we are using comint, we are limited by what comint can do.
Under the hood, comint uses stdin approach to send user
commands. Handling what is a command, what is not a command, and hot to
edit it is entirely under Emacs control.

I do not see a great benefit of re-implementing session support via
actual terminal. (I think we agree here).

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>