home | list info | list archive | date index | thread index

Re: miniconda3 start and stop scripts

  • Subject: Re: miniconda3 start and stop scripts
  • From: "John Nash (NCF)" <nashjc [ at ] ncf [ dot ] ca>
  • Date: Wed, 13 May 2026 18:52:27 -0400
I'll give sourcing a try, though "eval" was the syntax borrowed from what was added to .bashrc by the miniconda3 install. Probably tomorrow however -- miniconda is on a different machine from this one.

JN


On 2026-05-13 18:48, Ron via linux wrote:
Nash JC - NCF via linux wrote on 2026-05-13 15:04:

  eval "$__conda_setup"

I get things going and see the command prompt with prefix " (base)  "

The command '

conda deactivate

returns to normal prompt.
However, putting these in scripts doesn't work. I suspect calling scripts is not getting right info to the virtual environment.

This hints at the difference between sourcing and executing a script - shared environment is preserved when sourcing.

I suspect eval is doing something in a subshell?


What happens if you merely source the scripts instead of eval-ing them?



To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org
To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org
To visit the archives: https://lists.linux-ottawa.org