Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start in WT? #3617

Closed
Timothep opened this issue Nov 18, 2019 · 2 comments
Closed

Start in WT? #3617

Timothep opened this issue Nov 18, 2019 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Timothep
Copy link

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?

@Timothep Timothep added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 18, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 18, 2019
@zadjii-msft
Copy link
Member

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 #492.

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

@ghost
Copy link

ghost commented 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 ghost closed this as completed Nov 18, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 18, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants