Repository navigation
Integrated Terminal Window becomes active #1284
Description
Environment data
- VS Code version: 1.21.1
- Extension version (available under the Extensions sidebar): 2018.3.1 (29 Mar 2018)
- OS and version: Microsoft Windows 10 Pro 10.0.16299 Build 16299
- Python version (& distribution if applicable, e.g. Anaconda): 2.7
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Actual behavior
When running a Python script in debugger, the Terminal window receives focus every time, regardless of what window previously had focus.
Expected behavior
When the DEBUG CONSOLE is active, it remains active when a script is run.
Steps to reproduce:
- select "DEBUG CONSOLE"
- run program
- Observe that TERMINAL has focus. To see the content in DEBUG CONSOLE you have to click to activate that window.
Activity
brettcannon commentedon Apr 5, 2018
Do we control this, Don Jayamanne (@DonJayamanne) ?
DonJayamanne commentedon Apr 5, 2018
Ted Chapin (@tchapin)
In the past the extension used the
debug consoleas the default output. However we've changed this default behavior in recent versions (as that doesn't support user input and leads confusions amongst users).There are two solutions (open
launch.jsonto make the following changes):consoletononeThis will revert back to the previous behavior (integrated terminal will not be used for debugging).
internalConsoleOptionstoopenOnSessionStartBrett Cannon (@brettcannon) the setting
internalConsoleOptionsis something provided by VS Code, and that's what controls the display of the debug console. The problem is with the use of the terminal, focus goes to the terminal.No. However there are ways around this (as mentioned above).
Update interpreter display (#3)
Refactor environment extension activation checks to use shouldEnvExtH…