Hi Eric, > "Eric Schulte" wrote: >> Yes, I've noticed the shell session evaluation problems as well. I think >> one possible solution is for us to move from the current schema of echoing >> a babel-specific marker to indicate that evaluation has completed (which >> isn't working very well and is fairly ugly to boot) and move towards >> something more like what Dan has done with R, where the output is written >> to a file, and we check for that file to be created to signal the end of >> session based evaluation. > > Will that handle ssh remote execution? I still have no clue to do that via > the sh code blocks, but that's what I'm targetting to. Therefore, the need > for a session.: > > 1. code block to open the ssh connection > 2. code block with some code > 3. code block with other code > 4. code block with logout > > >> This is certainly something that needs to be addressed, however I for one >> won't have any time over the next week (I'm attending a conference). >> >> Rest assured this issue is in our inbox. :) > > Thanks a lot for your continuous support.
Just for your information... After having chased a problem for making Tramp work -- that was caused by an overriden PS1 setting --, here is how Tramp does: Tramp needs a special prompt, in order to distinguish command output and, hmm, the prompt. It does set PS1 to '$ ' (and $TERM to 'dumb'). Don't know if this could be a solution here: set the prompt (instead of letting it customizable)? Best regards, Seb -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode