Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable env activation in PowerShell using command prompt #2892

Merged
merged 15 commits into from
Oct 16, 2018

Conversation

DonJayamanne
Copy link

For #2732

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
  • Title summarizes what is changing
  • Has a news entry file (remember to thank yourself!)
  • Unit tests & system/integration tests are added/updated
  • [n/a] Any new/changed dependencies in package.json are pinned (e.g. "1.2.3", not "^1.2.3" for the specified version)
  • [n/a] package-lock.json has been regenerated by running npm install (if dependencies have changed)

@@ -0,0 +1 @@
Disable activation of Python Environments in PowerShell by shelling into command prompt and back into PowerShell.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Disable activation of conda environments in PowerShell."

@DonJayamanne
Copy link
Author

@brettcannon Please re-review

}
protected async waitForCommandToProcess(shell: TerminalShellType) {
// Give the command some time to complete.
// Its been observed that sending commands too early will strip some text off in VS Terminal.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"VS Terminal". You mean "VS Code Terminal"? Probably worth just saying "the terminal" and leave it at that.

@DonJayamanne DonJayamanne merged commit 542ae64 into microsoft:master Oct 16, 2018
DonJayamanne added a commit that referenced this pull request Oct 18, 2018
@DonJayamanne DonJayamanne deleted the issue2827PowerShell branch October 31, 2018 17:37
@lock lock bot locked as resolved and limited conversation to collaborators Jul 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants