Ihor Radchenko <yanta...@posteo.net> writes:
> The problem is that Bash can send incoming text like
>
> "prompt> " "prompt> " "prompt> output\n".
>
> "prompt> prompt> prompt> output\n".
Yes. And I've seen these "outputs" with ob-haskell too ...
>
> So, we cannot reliably distinguish your case from other possibly comint
> quirks based on newline.
>
> One possible fix could be replacing `comint-prompt-regexp' one more time
> at the very end in addition to `org-babel-comint-prompt-separator'.
If I understand correctly, you suggest to do one last replace on the whole
text (buffer-string). But, for ob-haskell, the current prompt regex is:
"^[[:alnum:].*_() |λ]*> "
(it starts with "^")
> We must also make `comint-prompt-regexp' more precise to avoid "lude> "
> being detected as a prompt.
If we need to do that for ob-haskell (when relying on the interpreter),
the cleanest way might be to redefine the set of possible prompts. ghci
is quite flexible:
GHCi, version 8.10.7
:set prompt <prompt> set the prompt used in GHCi
:set prompt-cont <prompt> set the continuation prompt used in GHCi
:set prompt-function <expr> set the function to handle the prompt
:set prompt-cont-function <expr>
set the function to handle the continuation
prompt
I'll keep thinking about how to solve this.
Do we have common design principles and/or generic tests that all
languages based on org-babel/ob-comint must pass ?
Thanks Ihor!
Bruno
>
> --
> 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>
