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

Enable sending input to terminal instance by wt.exe #12925

Closed
ZhiruiLi opened this issue Apr 18, 2022 · 4 comments
Closed

Enable sending input to terminal instance by wt.exe #12925

ZhiruiLi opened this issue Apr 18, 2022 · 4 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

@ZhiruiLi
Copy link

Description of the new feature/enhancement

Some times we need to control windows terminal through command line. For example: switch dir to a given path. Now the only way to do that is to open a new pane or tab through wt.exe. However, open a new pane or tab is very slow when using powershell, it will be faster if we can just send input to a existing terminal, like:

wt.exe -w 0 -S "cd ~/project/MyProj; git pull"

Proposed technical implementation details (optional)

@ZhiruiLi ZhiruiLi added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 18, 2022
@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 Apr 18, 2022
@zadjii-msft
Copy link
Member

Okay this might seem silly, but wt -w 0 send-input {whatever} seems a lot harder than just typing {whatever} at the commandline in the current window, right?

This sounds a lot like #9368, but I might need more context on your actual use case here

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Apr 18, 2022
@ZhiruiLi
Copy link
Author

ZhiruiLi commented Apr 19, 2022

Okay this might seem silly, but wt -w 0 send-input {whatever} seems a lot harder than just typing {whatever} at the commandline in the current window, right?

This sounds a lot like #9368, but I might need more context on your actual use case here

There are many case that we can't type in current window, for example: implementing a plugin in vscode to let current terminal cd to current file location. Or we can trigger commands execution from some launcher apps, and see result in current terminal. It's too heavy for these use cases to start new wnidows terminal instances, reuse existing instances will be much better.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Apr 19, 2022
@zadjii-msft
Copy link
Member

Okay yea that's on me. Must not have had enough coffee - I read "commandline" and automatically assumed you were already sitting at the Terminal window and wanted to run that commandline in the Terminal window 😝

/dup #9368

@ghost
Copy link

ghost commented Apr 19, 2022

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 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 Needs-Attention The core contributors need to come back around and look at this ASAP. labels Apr 19, 2022
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