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

Add optional infine-looping command-line parameter for WindowsTerminal profiles #11001

Closed
vini-nu opened this issue Aug 21, 2021 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Issue-Question For questions or discussion 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 Resolution-Answered Related to questions that have been answered

Comments

@vini-nu
Copy link

vini-nu commented Aug 21, 2021

Description of the new feature/enhancement

Add boolean parameter if WindowsTerminal profile's command line should repeat every 1s in case command finishes. This would be useful for automatically restarting openssh sessions on the same tab. Currently you need to clone tab and reopen it again.

Proposed technical implementation details (optional)

E.g. I tried to implement this by typing this command-line profile: while ($true) { ssh [email protected] -p 22 -i ~/.ssh/id_ed25519; start-sleep -seconds 1}

But it doesn't work. I get [error 0x80070002 when launching while ($true) { ssh [email protected] -p 22 -i ~/.ssh/id_ed25519; start-sleep -seconds 1}] error.

If profile's command-line infine-loop+delay would be integrated inside WindowsTerminal, then it would be easier appliable

Thank you for creating this greater alternative tool to PuTTY.

@vini-nu vini-nu added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 21, 2021
@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 Aug 21, 2021
@zadjii-msft
Copy link
Member

You know, I think the even easier way to implement this would be with #4379 or #3726. No need to have an infinite loop to keep trying the commandline, just a button would do well ☺️

/dup #3726
/dup #4379

Also, you might try setting the commandline to powershell -c while ($true) { ssh [email protected] -p 22 -i ~/.ssh/id_ed25519; start-sleep -seconds 1} or something like that. You need to make sure to set the commandline to powershell running that script

@ghost
Copy link

ghost commented Aug 23, 2021

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 labels Aug 23, 2021
@zadjii-msft zadjii-msft added Issue-Question For questions or discussion 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 Resolution-Answered Related to questions that have been answered and removed Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels Aug 23, 2021
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. Issue-Question For questions or discussion 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 Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

2 participants