A user in microsoft/vscode#192943 (comment) is using profile environments to try workaround source and run commands being added to shell history, leading to more problems:
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!
Shells have various ways of avoiding adding entries into history. For example in bash you can add a space to the start of the command to have it not enter history. There are also some HIST* variables that define how history behaviors which are worth a read.
A user in microsoft/vscode#192943 (comment) is using profile environments to try workaround source and run commands being added to shell history, leading to more problems:
Shells have various ways of avoiding adding entries into history. For example in bash you can add a space to the start of the command to have it not enter history. There are also some
HIST*variables that define how history behaviors which are worth a read.