Current Behavior

When using csh or tcsh only
After using "conda activate env" for the first time issuing "conda env list" adds the conda/bin directory as a prefix to the PATH variable causeing future python execution to use a non-intended python version.
Even worse: every time "conda env list is issued a new "conda/bin" is prefixed to the PATH variable.
The same issue happens when an conda command is executed the results in an error e.g "conda activate non_existing".

Steps to Reproduce

• setup conda for csh
• create a new environment "py"
• conda activate py
• 'which python` gives correct path to py/python executable
• conda env list
• 'which python` gives incorrect path to conda/bin/python

Expected Behavior

"conda env list" or any informational or invalid conda com and should not affect the PATH variable

Cause

This problem is caused by conda.csh line 29

It modifies the path environment variable. That change is reversed in cases when the
eval statements are executed (line 33,38 or 44) but if an error happens in lines (32, 37 or 43)
or if the "default:" statement is executed the path variable is left unchanged with the altered value.

Solution

The proposed solution stores the value of the Path variable and restores it in case of error or in the default branch of the switch statement when no "eval" statement is executed that would set the PATH variable correctly.