You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.env does not apply to fish when in pythonTerminalEnvVarActivation experiment #22005
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" ].
Hey Kyochikuto | キョウチクトウ (@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?
Thanks for the logs, looks like source /some/path/.venv/bin/activate.fish isn't sent anymore based on it which is expected in the experiment.
If you notice there's a line "Setting environment variable FISH_HISTORY in collection to" in the logs, this issue has been fixed in the latest pre-release (we now set fish_history instead of FISH_HISTORY), but I just noticed that it's only available on VS Code Insiders. Sorry about that.
If you could try https://code.visualstudio.com/insiders/ I'm positive this issue should go away, we'll release this fix in the stable VS Code in about a month.
Activity
Do not upper case custom env variables (#22004)
karrtikr commentedon Sep 15, 2023
Kyochikuto | キョウチクトウ (@kyochikuto) Fix should be out in the pre-release version of the extension, use the following to try it out:
karrtikr commentedon Sep 16, 2023
Hey Kyochikuto | キョウチクトウ (@kyochikuto) , if you still see
source /some/path/.venv/bin/activate.fishthen you're not in the experiment. Can you add that setting in User settings and reload window?karrtikr commentedon Sep 16, 2023
Try this, make sure to add it in User settings when using latest stable version of VS Code:
karrtikr commentedon Sep 16, 2023
Thanks for the logs, looks like
source /some/path/.venv/bin/activate.fishisn't sent anymore based on it which is expected in the experiment.If you notice there's a line "Setting environment variable FISH_HISTORY in collection to" in the logs, this issue has been fixed in the latest pre-release (we now set
fish_historyinstead ofFISH_HISTORY), but I just noticed that it's only available on VS Code Insiders. Sorry about that.If you could try https://code.visualstudio.com/insiders/ I'm positive this issue should go away, we'll release this fix in the stable VS Code in about a month.
Allow publish of pre-releases to VS Code stable this iteration (#22009)
Allow publish of pre-releases to VS Code stable this iteration (micro…
Merged PR posit-dev/positron-python#224: Merge/2023.18
Merged PR posit-dev/positron-python#224: Merge/2023.18