Maybe it is a naive point of view of a user, yet I cannot imagine that it is possible to switch cmd to Powershell at this point for years now, but not making the small step forward to replace these two items again with wt. The user can use the default console option to specify which shall be opened by default from there Update the ADMX file accordingly so it can be set via GPO, tooĬaveat: wt needs to be installed by the user Hi team, users, since wt has now very good set of options and a preset settings json and a user defineable part which also includes the setting, which console is the default console to be opened when launching wt - I thought it would be sufficient to pick up all the rough plans ( #492 (comment)) to pick up at least the following attempt:Ĭonnect with Jennifer Gentlemen and team for settingsĪdd a new settings item that is able to replace or update the following setting to launch wt instead powershell or cmd
What's wrong / what should be happening instead: The new command prompt should open in a new tab in the existing Terminal window. What you're doing and what's happening: When I type start in a command prompt session in the Windows Terminal, the new command prompt window opens in a new conhost window. Your Windows build number: Microsoft Windows
Please use this form and describe your issue, concisely but precisely, with as much detail as possible Instead, send dumps/traces to referencing this GitHub issue. Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. If you have a feature request, please post to the UserVoice. This bug-tracker is monitored by Windows Console development team and other technical types. This is not terminal-specific, but Windows Terminal will benefit from it. This issue tracks the work required to add "default terminal" support to Windows.
0 kommentar(er)
