-
Notifications
You must be signed in to change notification settings - Fork 35
Closed
Labels
area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
Description
Out team disables terminal integration because of performance and all-around quirkyness/bugs.
I've been really frustrated with constant prompting about adding shellStartup (maybe 50% of time when opening terminal). But could never replicate it when i tried to do it twice in a row.
Last week i would periodically check .bashrc, and find sometimes it was "cleared/reverted"
Today i noticed running the build tasked made it disappear from the .bashrc, and thus i get prompted the next time i go to open a terminal.
# >>> vscode python
# version: 0.1.1
if [ -z "$VSCODE_PYTHON_AUTOACTIVATE_GUARD" ]; then
export VSCODE_PYTHON_AUTOACTIVATE_GUARD=1
if [ -n "$VSCODE_PYTHON_BASH_ACTIVATE" ] && [ "$TERM_PROGRAM" = "vscode" ]; then
eval "$VSCODE_PYTHON_BASH_ACTIVATE" || true
fi
fi
# <<< vscode python
it seems if the task really needs to not activate because of incompatibility, it could do it used by controlling any of those three env-vars rather than stripping the .bashrc (without a prompt even)
Metadata
Metadata
Assignees
Labels
area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug