microsoft / microsoft/vscode-cpptools
"console": "externalTerminal" not re-using terminal window on relaunch.
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
Type: Bug
Issue troubleshooting has identified that the issue is with Visual Studio Code. It is confirmed that the issue exists in Visual Studio Code Insiders
The description for the launch.json setting "console": "externalTerminal":
"Console applications will be launched in an external terminal window. The window will be reused in relaunch scenarios and will not automatically disappear when the application exits.:"
The console is not reused in relaunch. Instead, a new terminal is created and the old window stays open waiting with "Press any key to continue...".
Steps to reproduce:
-
Create a launch.json configuration with the following settings:
"name": "(Windows) Launch",
"type": "cppvsdbg",
"request": "launch",
"program": "W:/build/w32_handmade.exe", // (this can be anything)
"args": [],
"stopAtEntry": false,
"cwd": "W:/data", // doesn't matter
"environment": [],
"console": "externalTerminal",
"preLaunchTask": "Build from ps1", // Doesn't affect
"internalConsoleOptions": "openOnFirstSessionStart" -
Launch the program and observe console output.
-
Close using the red X in the top right and relaunch.
-
Observe that the console is not reused.
If this behavior is intended, then the description of the setting should be changed. If it is not intended, please fix it.
Please follow up at:
suteegee@gmail.com
OR
jacksimunic2017@gmail.com
Thanks,
Jack.
Extension version: 1.22.9
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.22635
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 5 2600 Six-Core Processor (12 x 3400) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 15.95GB (3.37GB free) |
| Process Argv | . --crash-reporter-id 90992b4d-8b1a-4b23-984e-706a6ef2e88a |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
0ee40948:31013168
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31156134
notype1:31157159
5fd0e150:31155592
dwcopilot:31161677
icondisabled:31158250
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Riproduci il problema con la configurazione launch.json fornita usando cppvsdbg e impostando console su externalTerminal. Confronta il primo avvio, la chiusura della finestra esterna e il comportamento al riavvio; l'attività è completata quando la finestra del terminale documentata viene riutilizzata oppure la descrizione dell'impostazione riflette accuratamente il comportamento osservato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- cpp, typescript, vscode
- Ambito
- devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100