From: "Cook, Malcolm" <MEC@stowers.org>
To: "matt@excalamus.com" <matt@excalamus.com>,
Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"jackkamm@tatersworld.org" <jackkamm@tatersworld.org>
Subject: Re: [BUG] conda doesn't work in ob-shell sessions
Date: Wed, 23 Oct 2024 15:33:01 +0000 [thread overview]
Message-ID: <DS7PR20MB46710536E0EFB88FF7EDC427BE4D2@DS7PR20MB4671.namprd20.prod.outlook.com> (raw)
# -*- org-confirm-babel-evaluate: nil; -*-
I have been struggling with interrelated issues raised in
- https://list.orgmode.org/87jznda90u.fsf@localhost/#t
- https://list.orgmode.org/87le1bc8j3.fsf@localhost/
I expect I am using all the patches offered in addressing these given
my recent build from main. However, in my hands, I find they still
easily allow for mistakes identifying prompts in code block results.
In this demonstration, I am extending the approach to inquiry begun by Jack in
https://list.orgmode.org/87ttzn1mai.fsf@gmail.com/
#+begin_src emacs-lisp :results raw
(org-version nil t)
(emacs-version)
#+end_src
#+RESULTS:
GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.15.12, Xaw3d scroll bars)
of 2024-09-04
(Org mode version 9.7.10 (release_9.7.10 @ /home/mec/.local/share/emacs/31.0.50/lisp/org/) GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.15.12, Xaw3d scroll bars)
of 2024-09-04)
#+begin_src emacs-lisp
(org-babel-do-load-languages
'org-babel-load-languages
'((shell . t)))
#+end_src
#+RESULTS:
Here I define two org code blocks I will use repeatedly below:
#+name:test_filter
#+begin_src shell :session *shell* :results output
printf "a\nb\nc\n>d\n<e\nf>\nggg ggg>\nhhh hhh+\na\n"
#+end_src
#+name:shell_prompt_info
#+begin_src elisp
(with-current-buffer "*shell*"
(format "[comint-prompt-regexp]=[%s]\n[org-babel-comint-prompt-regexp-old]=[%s]" comint-prompt-regexp org-babel-comint-prompt-regexp-old))
#+end_src
#+caption: The results looks good - the output apparently is not confused as being prompt.
#+call: test_filter()
#+RESULTS:
: a
: b
: c
: >d
: <e
: f>
: ggg ggg>
: hhh hhh+
: a
#+caption: take a look at the prompt variables.
#+call:shell_prompt_info()
#+RESULTS:
: [comint-prompt-regexp]=[^org_babel_sh_prompt> *]
: [org-babel-comint-prompt-regexp-old]=[^[^#$%>
: ]*[#$%>] *]
#+caption: check on conda's availabiity & version
#+begin_src shell :session *shell* :results output
conda --version
#+end_src
#+RESULTS:
: conda 24.7.1
#+begin_src shell :session *shell* :results output
conda create --yes --name myenv python=3.9
#+end_src
#+RESULTS:
#+begin_example
... abbreviated...
To activate this environment, use
conda activate myenv
To deactivate an active environment, use
conda deactivate
#+end_example
#+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()
#+RESULTS:
: a
: b
: c
: d
: <e
:
: hhh hhh+
: a
#+caption: Observe the prompts have changed. Perhaps this is related issue?
#+call:shell_prompt_info()
#+RESULTS:
: [comint-prompt-regexp]=[^[^#$%>
: ]*[#$%>] *]
: [org-babel-comint-prompt-regexp-old]=[^org_babel_sh_prompt> *]
#+caption: can we restore by deactivating the environment?
#+begin_src shell :session *shell* :results output
conda activate
#+end_src
#+RESULTS:
#+caption: alas, no:
#+call: test_filter()
#+RESULTS:
: a
: b
: c
: d
: <e
:
: hhh hhh+
: a
#+caption: how about by resetting the prompt
#+begin_src shell :session *shell* :results output
PROMPT_COMMAND=;PS1="org_babel_sh_prompt> ";PS2=
#+end_src
#+RESULTS:
#+caption: alas, again, no
#+call: test_filter()
#+RESULTS:
: a
: b
: c
: d
: <e
:
: hhh hhh+
: a
#+caption: perhaps restoring the prompt variables will recover?
#+begin_src elisp
(with-current-buffer "*shell*"
(setq-local comint-prompt-regexp "^org_babel_sh_prompt> *"
org-babel-comint-prompt-regexp-old "[^[^#$%>
]*[#$%>] *"))
#+end_src
#+RESULTS:
: [^[^#$%>
: ]*[#$%>] *
#+caption: YES!
#+call: test_filter()
#+RESULTS:
: a
: b
: c
: >d
: <e
: f>
: ggg ggg>
: hhh hhh+
: a
In the above, I am exclusively allowing org/ob/comint to "own" the shell
buffer, and not interact with it, as recommended earlier by Ivor.
I have tried the above after first calling `(shell)` and find
variations on the above occur. I would like to be able to 'share' the
*shell* buffer with org/ob/comint but expect resolving the
non-interactive case should possibly lay foundation.
I would additional like to layer in working with remote shells
(e.g. `:dir "/ssh:me@host:~/`) and have tried but this is just
layering in complexity on the localhost case so I'm backing off for
now.
What else can I report or test?
next reply other threads:[~2024-10-23 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 15:33 Cook, Malcolm [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 19:39 [PATCH] Async evaluation in ob-shell Matt
2023-02-11 20:56 ` jackkamm
2023-02-12 19:02 ` Matt
2023-02-13 3:16 ` Jack Kamm
2023-02-13 20:11 ` [BUG] conda doesn't work in ob-shell sessions Matt
2023-02-15 6:21 ` Jack Kamm
2024-01-18 11:55 ` Ihor Radchenko
2024-01-21 22:48 ` Jack Kamm
2024-01-22 3:42 ` Jack Kamm
2024-01-22 11:59 ` Ihor Radchenko
2024-01-23 6:09 ` Jack Kamm
2024-01-24 15:22 ` Ihor Radchenko
2024-01-25 19:14 ` Matt
2024-01-25 20:36 ` Ihor Radchenko
2024-01-26 0:42 ` Jack Kamm
2024-01-27 10:25 ` Matt
2024-02-09 16:37 ` Ihor Radchenko
2024-01-23 18:51 ` Suhail Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DS7PR20MB46710536E0EFB88FF7EDC427BE4D2@DS7PR20MB4671.namprd20.prod.outlook.com \
--to=mec@stowers.org \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@tatersworld.org \
--cc=matt@excalamus.com \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).