>>>> #+begin_src sh >>>> printf 'a\nb\nc\n>d\n<e\n' >>>> #+end_src >>>> >>>> #+RESULTS: >>>> : a >>>> : b >>>> : c >>>> : d >>>> : <e >>>> >>>> Huh? what happened to the ">" before the "d"? >>> >>>I cannot reproduce. >>>May it be that you are setting global :session header argument? >> >> Yes, of course, so sorry, there is >> >> #+PROPERTY: header-args:sh :session *shell* :results output >> >> You should now be able to reproduce. >> >> Thanks, please let me know if you have a fix, workaround, or lesson for me. > >In theory, we may provide a workaround for this kind of problem. But it >would have pros and cons. > >The underlying cause is limitation of Emacs API for interactive shells - >we cannot easily distinguish command output from prompt and other extra >staff your shell/other interactive command spits into the buffer. >So, we have to either filter output the prompts ourselves to get the >command output reliably or redirect output to files, where nothing >litters the actual output with prompts.
Yeah, I've noticed this also especially with Org as it relates to R and ESS. > >Redirecting output works fine when we do not use sessions and do not >care what is displayed in the *shell* buffer for users. For sessions, we >use more complex approach - filter out anything that looks like prompt. > >The problem with bash is that prompt is ">", and, as you showed in your >example, having ">" in the commands output breaks everything. > >Again, we know this problem, and we normally force the prompt to be >something more unique when creating sessions. But we do not touch the >prompt when you point Org to an existing interactive shell buffer - that >could be a surprise if Org mode changes the prompts by force in the >shells you use interactively. > >TL;DR: It is complicated. When we pull one string out, several more >get entangled. Might there be a solution wherein both the interactive shell buffer and Org are talking to a common underlying process? I would expect such to be significantly more complicated, but perhaps better factored? Not that I'm offering or capable of such a re-write 😉 >As a practical workaround, just do not use *shell* session names and >session names that are the same as shell buffers you create manually. Is there perhaps another practical workaround you might suggest to me involving a more intentional setting of the prompt and/or informing Org of my choice of prompt (e.g. perhaps via setting a regexp to detect exactly my prompt, and only when it is anchored to beginning of line)? Thanks so much for your careful explanation and pointers, and of course all the work you do for Org ecosystem. Perhaps time for my 1st trip to liberapay... 😉 ~ Malcolm > >-- >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> >
