Re: bash source code block: problem after ssh commands

[Ihor Radchenko <yantar92@posteo.net>]

Max Nikulin <manikulin@gmail.com> writes:

> https://debbugs.gnu.org/67259
>
> Notice that the report is for *interactive* sessions. Org babel sessions 
> are not so interactive. They are to maintain state, not to interact with 
> users directly...

You are not right. We have legitimate cases when people can switch to
session buffer, enter commands there, switch back to Org buffers,
send code blocks to the same session, and so on.

> ...
> Possible voluntary decision is to consider every session source block 
> similar to "C-x C-e" in bash prompt, so nothing should become implicit 
> stdin of commands. Content of a source block should be saved into a 
> temporary file then "source /path/to/block_content" command should be 
> send to the session buffer. Likely command depends on shell.

This may work, but we should at least echo the original commands into
session buffer, because users may want to examine them.

-- 
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>