Activating a conda environment using `conda` instead of `source`

Environment data

• VS Code version: 1.23.1
• Extension version (available under the Extensions sidebar): 2018.5.0
• OS and version: Linux Manjaro 4.16.13-1
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.3 / conda version: 4.5.2
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda

Actual behavior

I am using the zsh shell. When I create a new python terminal it uses source activate 'name_of_environment'

Expected behavior

I am using the zsh shell. When I create a new python terminal it uses conda activate 'name_of_environment

Steps to reproduce:

1. install latest conda
2. add “. /etc/profile.d/conda.sh” to your .zshrc file as recommended by any conda version after 4.4
3. try to create a new python terminal within vscode whille the activateEnviroment setting is true

[ericsnowcurrently]

BTW, I tried out miniconda 4.4.0+ on Windows and it worked fine. So we don’t need to change anything there.

[DonJayamanne]

@d3r3kk

I’d close #2315 and keep this open, as this has the original issue and the solution. (I.e. mentioned the new way of activation). #2315 merely mentioned another symptom.