Conda Activation in New Terminal on Mac OS

[chrisjsewell]

Environment data

• VS Code version: 1.30.2
• Extension version: 2018.12.1
• OS and version: Mac OS 10.10.5
• Python version : 2.7.15
• Conda: 4.5.11-py27_0

Expected behaviour

When opening a new terminal, with a conda environment selected,
the conda environment should be activated:

>> source activate env-name

(env-name) >>

or

>> source /anaconda/envs/env-name/bin/activate env-name

(env-name) >>

Actual behaviour

When the current automated command is run, it only loads the base environment:

>> source /anaconda/envs/env-name/bin/activate

(base) >>

This may actually be a bug in conda, but the activation scripts in both /anaconda/bin/activate
and /anaconda/envs/env-name/bin/activate are the same:

#!/bin/sh
_CONDA_ROOT="//anaconda"
\. "$_CONDA_ROOT/etc/profile.d/conda.sh" || return $?
_conda_activate "$@"

Steps to reproduce:

1. Open new terminal with conda environment selected.

[DonJayamanne]

Duplicate of #4001