starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request - Easier means of launching Windows Terminal #2001

New Issue
Closed
opened 2026-01-30 22:44:03 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 22:44:03 +00:00
Owner
Copy Link

Originally created by @JaimeStill on GitHub (Jun 23, 2019).

Summary of the new feature/enhancement

Most of the time, when I open a command prompt, I either run cmd from the navbar of the directory I want to open in Windows Explorer, or I run cmd from the Run utility (Win + R).

It would be great if one of the solutions outlined below would allow better integration of Windows Terminal, making it a more viable shell for use in Windows.

Proposed technical implementation details (optional)

Default Shell
In Windows 10, you have the option of setting application defaults. A Shell category could be added and linked to Windows Terminal. This way, any time you launch PowerShell, Command Prompt, or any other CLI, it will launch in Windows Terminal. I know OS-wide settings are outside of the scope of this project, but I think it is a good conversation to have regarding people who want to use this tool by default at the operating system level.

terminal-settings

Alternative Solution
Provide a way to launch Windows Terminal in the same way you can use cmd to launch Command Prompt (as specified above).

Originally created by @JaimeStill on GitHub (Jun 23, 2019). # Summary of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> Most of the time, when I open a command prompt, I either run `cmd` from the navbar of the directory I want to open in Windows Explorer, or I run `cmd` from the Run utility (<kbd>Win + R</kbd>). It would be great if one of the solutions outlined below would allow better integration of Windows Terminal, making it a more viable shell for use in Windows. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> **Default Shell** In Windows 10, you have the option of setting application defaults. A **Shell** category could be added and linked to Windows Terminal. This way, any time you launch PowerShell, Command Prompt, or any other CLI, it will launch in Windows Terminal. I know OS-wide settings are outside of the scope of this project, but I think it is a good conversation to have regarding people who want to use this tool by default at the operating system level. ![terminal-settings](https://user-images.githubusercontent.com/14102723/59979059-a49c4c00-95b0-11e9-9eb1-8667f2ac276e.png) **Alternative Solution** Provide a way to launch Windows Terminal in the same way you can use `cmd` to launch Command Prompt (as specified above).
claunia commented 2026-01-30 22:44:04 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

instead of cmd, type wt

I either run cmd from the navbar of the directory I want to open in Windows Explorer, or I run cmd from the Run utility (Win + R).

@Shorotshishir commented on GitHub (Jun 23, 2019): instead of `cmd`, type `wt` > I either run cmd from the navbar of the directory I want to open in Windows Explorer, or I run cmd from the Run utility (Win + R).
claunia commented 2026-01-30 22:44:04 +00:00
Author
Owner
Copy Link

@JaimeStill commented on GitHub (Jun 23, 2019):

@Shorotshishir thanks, I didn't find any mention of this on my initial tinkering. This is definitely helpful! However, it does not work for resolving the current directory when launching from the navigation bar in Explorer.

@JaimeStill commented on GitHub (Jun 23, 2019): @Shorotshishir thanks, I didn't find any mention of this on my initial tinkering. This is definitely helpful! However, it does not work for resolving the current directory when launching from the navigation bar in Explorer.
claunia commented 2026-01-30 22:44:04 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

@JaimeStill use "startingDirectory" : "%CD%". your issue will be resolved.
image

@Shorotshishir commented on GitHub (Jun 23, 2019): @JaimeStill use "startingDirectory" : "%__CD__%". your issue will be resolved. ![image](https://user-images.githubusercontent.com/16465879/59979713-e65ae000-960c-11e9-9914-ae6b1cdd0bf0.png)
claunia commented 2026-01-30 22:44:04 +00:00
Author
Owner
Copy Link

@ducaale commented on GitHub (Jun 23, 2019):

@Shorotshishir is it possible to use %__CD__% only when launching from the navigation bar in Explorer and use %PROFILE% when launching from start menu?

@ducaale commented on GitHub (Jun 23, 2019): @Shorotshishir is it possible to use %\_\_CD\_\_% only when launching from the navigation bar in Explorer and use %PROFILE% when launching from start menu?
claunia commented 2026-01-30 22:44:04 +00:00
Author
Owner
Copy Link

@JaimeStill commented on GitHub (Jun 24, 2019):

@ducaale @Shorotshishir having the ability to differentiate the two scenarios would definitely be ideal.

@JaimeStill commented on GitHub (Jun 24, 2019): @ducaale @Shorotshishir having the ability to differentiate the two scenarios would definitely be ideal.
claunia commented 2026-01-30 22:44:05 +00:00
Author
Owner
Copy Link

@Dinjoralo commented on GitHub (Jun 24, 2019):

I'm guessing this will come later when the Terminal is closer to being out of preview, but a way to just have this popup whenever CMD/Powershell/WSL would open would be nice.

@Dinjoralo commented on GitHub (Jun 24, 2019): I'm guessing this will come later when the Terminal is closer to being out of preview, but a way to just have this popup whenever CMD/Powershell/WSL would open would be nice.
claunia commented 2026-01-30 22:44:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

Right now, wt is the "easier" way to launch wt. If you're using a dev build, it's wtd. This'll be better served by #492.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): Right now, `wt` is the "easier" way to launch `wt.` If you're using a dev build, it's `wtd`. This'll be better served by #492.
claunia commented 2026-01-30 22:44:05 +00:00
Author
Owner
Copy Link

@ledhed-jgh commented on GitHub (Aug 6, 2019):

While this is actually the opposite of "Launching" Windows Terminal, it would be great if you could close the current tab (Powershell or CMD) with CTRL+D. This is very common on Linux shells like Bash.

@ledhed-jgh commented on GitHub (Aug 6, 2019): While this is actually the opposite of "Launching" Windows Terminal, it would be great if you could close the current tab (Powershell or CMD) with CTRL+D. This is very common on Linux shells like Bash.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Issue-Docs Issue-Feature Product-Terminal Resolution-Won't-Fix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2001
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?