Terminal Issues

[DonJayamanne]

• Terminal Activation:

  • Activation script sent to terminal after debugger starts Debugging fails when using a pipenv environment that gets activated with pipenv shell #4203, Spike - Activation script sent to terminal after debugger starts (Use Conda run) #5664
  • Slow activation causes issues Enhancement: Prevent keyboard input to new terminals when activating environments #4558, Debugging fails when using a pipenv environment that gets activated with pipenv shell #4203, Run python file in pipenv environment fails #4245
  • Ensure it works in latest Conda for Powershell (I think we disable it) Change activation of conda environments in powershell #668
  • Multiroot not working Auto activation of environments does not work with multi root workspaces #3325
  • Activation is slow when debugging Environment gets activated after debugger starts (hence debugging with conda envs fail) #5559

• Misc

  • Escaping characters: Run Python File In Terminal doesn't escape special chars in pathnames #4165
  • Powershell permissions Activating an environment fails because running powershell scripts is disabled by default on Windows #2559

• Enhancements:

  • Pyenv + virtual env activation pyenv + virtualenv not working - use pyenv activate for all  #4013
  • Global activation (for envs without activation scripts) Set the user-installed bin directory when "activating" a terminal #1765

[luabud]

@DonJayamanne Shouldn't #5539 be tracked here as well? Doesn't seem to be DS specific.

[DonJayamanne]

@luabud I've added #5539 into #7425

[karrtikr]

Closing as most of the issues in the list are fixed.