Note that if you use conda then there is no need for sage-the-distro (and thus, in particular, for the sage shell env init). In particular, if you install sage via conda (conda create -n sage sage) then you only have a "sage" script/cli available if you first activate the conda env (conda activate sage). We could add to the documentation instructions on how to setup a custom subshell that automatically activates the sage conda env. I like that idea. Without trying, a bash script with ` #!/usr/bin/env conda run -n sage sage` should do the job.
That almost works! It starts sage but then it exists, so it looks like STDIN doesn't get properly connected (which means it's actively disconnected). What seems to work for now is to just run /opt/sage/miniforge3/envs/sage/bin/sage (without letting conda do any environment setup!). That's just the standard sage startup script, so it sources sage-env. It could be more fragile than allowing conda to activate its environment properly, so it's probably preferable to involve "conda run" somehow. It would require a version of "conda run" that does connect STDIN properly, so really just something that doesn't mess with the standard streams. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/ffeeefbb-6bed-4867-8a2b-746f776bbfeen%40googlegroups.com.
