Not honoring conda virtual envs.

[sccolbert]

Is there a way to disable Terminus from inheriting Sublimes env, and using the default shell env? This is required to pickup conda virtual envs. VSCode has a setting for this to make their terminals work.

OSX Terminal:

(base) Chriss-iMac:~ chris$ which python
/Users/chris/miniconda3/bin/python

Terminus:

(base) Chriss-iMac:~ chris$ which python
/usr/bin/python  

[randy3k]

What shell are you using? What do you mean the default shell env? In default, Terminus opens a bash shell with login in flag. Did you set the PATH variable in bash (or whatever you have) profile?

[sccolbert]

It's bash with a bash_profile that sets up the virtual env(s). It's seems that profile script is executing differently in terminus vs terminal.

[sccolbert]

link to VSCode issue: microsoft/vscode-python#7607

[randy3k]

We don’t need that to fix the PATH issue. How did you specify the PATH variable in.bash_profile? Or you have set it in a different way?

[sccolbert]

It's not actually set in .bash_profile. The .bash_profile eventually calls out to conda, which is a Python script, which does quite a bit of logic to set up the bath. I think that one of things it does is tries to be smart and not clobber the PATH env if it's been inherited from a parent, hence the solution VSCode is using. I only mentioned the VSCode issue because the behavior it presented is exactly the same as what I'm seeing in Terminus.

[randy3k]

It's not actually set in .bash_profile.
So how it was set in the macOS Terminal?

The .bash_profile eventually calls out to conda, which is a Python script, which does quite a bit of logic to set up the bath.

conda doesn't setup the PATH variable, it is controlled by the shell profile. Look for something like export PATH="$HOME/miniconda3/bin;$PATH". If it doesn't present, just add it.

I think that one of things it does is tries to be smart and not clobber the PATH env if it's been inherited from a parent, hence the solution VSCode is using. I only mentioned the VSCode issue because the behavior it presented is exactly the same as what I'm seeing in Terminus.

Not inheriting the env variables is just a temporary solution to fix your issue of the PATH variable. I am not saying that it would not fix the issue. For sure that it will help the situation. But you also need to figure out the ultimate reason why the PATH was not set correctly and it will save you more time in the future.