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: Add a unique launch argument for Windows Terminal Preview #9446

New Issue
Closed
opened 2026-01-31 01:54:43 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:54:43 +00:00
Owner
Copy Link

Originally created by @yaira2 on GitHub (Jul 5, 2020).

Description of the new feature/enhancement

Right now, both the release version and preview version of Terminal use the same launch arguments wt and the dev version uses wtd. While it's possible to set wt to point to the preview instead of the release version, there are times when I want to be able to launch either of them using launch arguments. An example where this would be useful is the navigation textbox in Files Explorer where I can type in cmd, wt and other similar commands.

Proposed technical implementation details (optional)

A solution would be to add a unique launch argument for the preview version such as wtp so that I can continue using wt for the release version and wtd for the dev version.

Originally created by @yaira2 on GitHub (Jul 5, 2020). # Description of the new feature/enhancement Right now, both the release version and preview version of Terminal use the same launch arguments `wt` and the dev version uses `wtd`. While it's possible to set `wt` to point to the preview instead of the release version, there are times when I want to be able to launch either of them using launch arguments. An example where this would be useful is the navigation textbox in Files Explorer where I can type in `cmd`, `wt` and other similar commands. # Proposed technical implementation details (optional) A solution would be to add a unique launch argument for the preview version such as `wtp` so that I can continue using `wt` for the release version and `wtd` for the dev version.
claunia commented 2026-01-31 01:54:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 16, 2020):

I'm not horribly opposed to this idea. That being said, I'd love to better understand why you might want to be running both at the same time. I'd think that if you are the kind of person to want the preview version and release cadence, then you'd probably always want to use the preview one, right?

@zadjii-msft commented on GitHub (Jul 16, 2020): I'm not _horribly_ opposed to this idea. That being said, I'd love to better understand why you might want to be running both at the same time. I'd think that if you are the kind of person to want the preview version and release cadence, then you'd probably _always_ want to use the preview one, right?
claunia commented 2026-01-31 01:54:45 +00:00
Author
Owner
Copy Link

@yaira2 commented on GitHub (Jul 16, 2020):

@zadjii-msft I personally use both as I like to keep up to date with the latest features, but I like having the release version as a backup in case there is an issue with the preview version.

@yaira2 commented on GitHub (Jul 16, 2020): @zadjii-msft I personally use both as I like to keep up to date with the latest features, but I like having the release version as a backup in case there is an issue with the preview version.
claunia commented 2026-01-31 01:54:45 +00:00
Author
Owner
Copy Link

@lukeblevins commented on GitHub (Jul 17, 2020):

@zadjii-msft If both apps have a different release cadence, then why have the same executable name? 😃

@lukeblevins commented on GitHub (Jul 17, 2020): @zadjii-msft If both apps have a different release cadence, then why have the same executable name? 😃
claunia commented 2026-01-31 01:54:45 +00:00
Author
Owner
Copy Link

@jaigak commented on GitHub (Jul 20, 2020):

@zadjii-msft If both apps have a different release cadence, then why have the same executable name? 😃

The can't keep changing the name of the executable.

@jaigak commented on GitHub (Jul 20, 2020): > @zadjii-msft If both apps have a different release cadence, then why have the same executable name? 😃 The can't keep changing the name of the executable.
claunia commented 2026-01-31 01:54:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 28, 2020):

So, I'm going to reject this request. Sorry.

Preview and Stable are only intended to be installed side-by-side and switched between when you're worried about the stability of Preview. We're not intending both channels to be in active simultaneous use. If you're encountering an issue that means you make to switch between them more than once in a single session I'd rather we just fix the issue instead of bandaging it with another app execution alias. If you are, please do let us know what those issues are.

Fortunately, you can work around this yourself! If you link %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe somewhere in your path as wtp (or create a batch file called wtp.cmd, or any number of other tricks), you can explicitly launch it as wtp whenever you want. You can bind a shortcut to that specific path and it'll be durable for the life of the application.

@DHowett commented on GitHub (Jul 28, 2020): So, I'm going to reject this request. Sorry. Preview and Stable are only intended to be installed side-by-side and switched between when you're worried about the stability of Preview. We're not intending both channels to be in active simultaneous use. If you're encountering an issue that means you make to switch between them _more than once in a single session_ I'd rather we just fix the issue instead of bandaging it with another app execution alias. If you are, please do let us know what those issues are. Fortunately, you _can_ work around this yourself! If you link `%LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\wt.exe` somewhere in your path as _wtp_ (or create a batch file called wtp.cmd, or any number of other tricks), you can explicitly launch it as wtp whenever you want. You can bind a shortcut to that specific path and it'll be durable for the life of the application.
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-Commandline Issue-Task Needs-Attention 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#9446
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?