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

Start in WT? #5059

New Issue
Closed
opened 2026-01-31 00:03:58 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:03:58 +00:00
Owner
Copy Link

Originally created by @Timothep on GitHub (Nov 18, 2019).

I'm not sure if this is already a way to do this or not...

I have two long running python scripts that I run from Powershell. Instead of opening two PS Windows and then calling the the scripts manually, I created a batch file that spins up two instances of Powershell and calls the scripts on each:

start powershell -noexit -executionpolicy remotesigned .\some_path\script.py -somearguments

I was wondering if there is a way to tell it to spin the Powershell windows inside the new Windows Terminal?

Originally created by @Timothep on GitHub (Nov 18, 2019). I'm not sure if this is already a way to do this or not... I have two long running python scripts that I run from Powershell. Instead of opening two PS Windows and then calling the the scripts manually, I created a batch file that spins up two instances of Powershell and calls the scripts on each: `start powershell -noexit -executionpolicy remotesigned .\some_path\script.py -somearguments` I was wondering if there is a way to tell it to spin the Powershell windows inside the new Windows Terminal?
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:03:58 +00:00
claunia commented 2026-01-31 00:03:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 18, 2019):

Funnily enough, I literally just replied to an internal mail thread on this exact question. From that thread:

It might be more possible once commandline args (#607/#3495) lands, though that’s not really slated for 1.0. With that, you'd be able to call wt.exe <some command> and have that run <some command> in a Windows Terminal window.
We do have plans to enable users to configure their “default terminal emulator” on Windows, though that won’t land for a while. You can track the that request at microsoft/terminal#492.

Broadly, this is a /dup of #492, so I'll direct conversation to that thread. Thanks!

@zadjii-msft commented on GitHub (Nov 18, 2019): Funnily enough, I literally _just_ replied to an internal mail thread on this exact question. From that thread: > It _might_ be more possible once commandline args (#607/#3495) lands, though that’s not really slated for 1.0. With that, you'd be able to call `wt.exe <some command>` and have that run `<some command>` in a Windows Terminal window. > We do have plans to enable users to configure their “default terminal emulator” on Windows, though that won’t land for a while. You can track the that request at microsoft/terminal#492. Broadly, this is a /dup of #492, so I'll direct conversation to that thread. Thanks!
claunia commented 2026-01-31 00:04:00 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 18, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 18, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Issue-Feature Resolution-Duplicate
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#5059
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?