"Cook, Malcolm" <m...@stowers.org> writes: > #+begin_src shell :session *shell* :results output > conda create --yes --name myenv python=3.9 > #+end_src > ... > #+begin_src shell :session *shell* :results output > conda activate myenv > #+end_src > > #+RESULTS: > > #+begin_src shell :session *shell* :results output > which python > #+end_src > > #+RESULTS: > : > /n/projects/mec/SRSCHPC2/local/inst/Mambaforge/24.3.0-0/envs/myenv/bin/python > > #+caption: alas, the output of test_filter is changed. Some lines are gone > missing and some are changed. > #+call: test_filter() > ...
This is likely because conda changes the prompt, which Org mode does not expect. I am afraid that there is no general magic solution to detecting prompts. We either try heuristics and hit false-positives (that's what we did in the past) or set very specific prompt and try to search it (now). In the latter case, any changes to the prompt will break things. What can be done is force-setting the prompt every single time babel sends output to the comint buffer, but it feels wrong. -- Ihor Radchenko // yantar92, Org mode maintainer, 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>
