Skip to content

Commit 1c38b55

Browse files
authored
Update external Console notes
Updated external console option to show changes to support for integratedTerminal.
1 parent e12bad5 commit 1c38b55

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

launch.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,9 @@ Set or change the following options to control VS Code's behavior during debuggi
2222
Tells _GDB or LLDB_ what paths to search for .so files. Separate multiple paths with a semicolon. Example: `"/Users/user/dir1;/Users/user/dir2"`.
2323

2424
* #### `externalConsole`
25-
If set to `true`, launches an external console for the application. If `false`, no console is launched and VS Code's debugging console is used. Note this option is ignored in some cases for technical reasons.
25+
Windows: When set to true, it will spawn an external console. When set to false, it will use VS Code's integratedTerminal.
26+
Linux: When set to true, it will notify VS Code to spawn an external console. When set to false, it will use VS Code's integratedTerminal
27+
macOS: When set to true, it will spawn an external console through `lldb-mi`. When set to false, the output can be seen in VS Code's debugConsole. Due to limitations within `lldb-mi`, integratedTerminal support is not available.
2628

2729
* #### `logging`
2830
Optional flags to determine what types of messages should be logged to the Debug Console.

0 commit comments

Comments
 (0)