`.env` does not apply to fish when in `pythonTerminalEnvVarActivation` experiment

[karrtikr]

I actually need this to prevent VS Code from cluttering my shell history, otherwise my history is filled up with entries such as source /some/path/.venv/bin/activate.fish and /some/path/.venv/bin/python /some/path/src/myscript.py or subsequent commands I tried for that specific project which are irrelevant as my shell history in my general day to day usage!

Setting terminal.integrated.shellIntegration.history to 0 did not have any effect, at least on my fish shell, not sure if it's a bug or I'm missing something! Nor did having fish_history= in a .env file and opting into the newly introduced "python.experiments.optInto": [ "pythonTerminalEnvVarActivation" ].

Originally posted by @kyochikuto in microsoft/vscode#192943 (comment)

[karrtikr]

@kyochikuto Fix should be out in the pre-release version of the extension, use the following to try it out:

Updated to pre-release and tried but to no avail! I still see source /some/path/.venv/bin/activate.fish but this time I see my variable injected for the execution command /some/path/.venv/bin/python MYVAR=MYVAL /some/path/src/myscript.py which comes in a wrong place considering the purpose and also will not stop previous commands such as the source .. from inserting in the history, I guess this should be fixed in VSCode core and not the extension, nevertheless thank you for your time and efforts! Keep up the good job! ;)

[karrtikr]

Hey @kyochikuto , if you still see source /some/path/.venv/bin/activate.fish then you're not in the experiment. Can you add that setting in User settings and reload window?

[karrtikr]

Try this, make sure to add it in User settings when using latest stable version of VS Code:

"python.experiments.optInto": ["pythonTerminalEnvVarActivation"]