ThomasMarwitzQC
commented
10 months ago I found a solution to automatically activate an environment specified by an environment.yml file through micromamba in VSCode's integrated terminal.
First, turn off the automatic activation of conda envs: https://github.com/prefix-dev/pixi/discussions/415#discussioncomment-7393489
I then used this solution from Stack Overflow to execute a custom command every time an integrated terminal is launched. The answer suggests to include a conditional execution in your zsh/bash setup.
My updated .zshrc:
# This function uses micromamba to activate an environment that is specified in `environment.yml`.
function ma {
if [ -f environment.yml ]; then
env_name=$(cat environment.yml | yq .name)
if [ "$env_name" = "null" ] || [ -z "$env_name" ]; then
echo "Error: No environment name defined."
return 1
else
mm activate "$env_name"
fi
else
echo "Error: 'environment.yml' file not found."
return 1
fi
}
alias activate_micromamba_env='ma' # better output when launching VSCode's integrated terminal
# ...
# Used in VSCode's integrated terminal
if [[ -n $ZSH_INIT_COMMAND ]]; then
echo "Running: $ZSH_INIT_COMMAND"
eval "$ZSH_INIT_COMMAND"
fiI then added the following configuration to user settings in VSCode:
{
# ...
"terminal.integrated.env.osx": {
"ZSH_INIT_COMMAND": "activate_micromamba_env"
},
}When launching a new integrated terminal, the variable is set and executed (as specified in my .zshrc):
Running: activate_micromamba_env
(mytestenv) -------------------------------------------------------------------------------------------------------------------
~/Documents/Q/testproject » 
yanxiang-wang
GZTimeWalker
Let's collect some setup instructions here. I want to make a proper docs page from that