microsoft / microsoft/vscode-cmake-tools

FR: support the terminal.integrated.automationProfile.* when launch target without debug

Open
#3,756 0 comments 0 reactions 0 assignees View on GitHub
enhancement Feature: debug/launch
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Brief Issue Summary

Currently, it seems cmake tools use the vscode default integrated terminal to launch the target without debug, I set the

```
"terminal.integrated.defaultProfile.windows": "PowerShell",
"terminal.integrated.automationProfile.windows": {
"path": "C:\\Windows\\system32\\cmd.exe"
}
```
The idea is want to improve the launching terminal speed since I have powershell settings to make lanuching powershell is quite slow than cmd.

So, shall cmake tools suport to use the automationProfile setting? It may be a new bool setting to switch using of defaultProfile and automationProfile.

Or, cmake tools already provide some workaround for this idea? I didn't find the way after some study.

### CMake Tools Diagnostics

_No response_

### Debug Log

_No response_

### Additional Information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the launch target without debug selects VS Code's integrated terminal, then compare terminal.integrated.defaultProfile.* with terminal.integrated.automationProfile.*. Done means CMake Tools can use the automation profile for this launch path, with the proposed choice or setting documented and verified without disrupting the existing default profile behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.