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

quick command binding like xshell #6928

Closed
wfireleaves opened this issue Jul 15, 2020 · 2 comments
Closed

quick command binding like xshell #6928

wfireleaves opened this issue Jul 15, 2020 · 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

@wfireleaves
Copy link

What & Why

Using binding keys to input some commands or just a string to terminal. It's very useful for common commands and complex commands.

Type 'ctrl+1' to actually input a common command like 'ps -ef | grep server | grep -v grep'
It also can use to send command to all opened tab.

How

By using setting keys binding. we can set a new command action like 'input', we can bind it to keys like 'ctrl+0~ctrl+9' or any other keys.
for example.

{
	"command":{"action":"input", "argument":"my common command 1"},
	"keys":["ctrl+1"]
}
@wfireleaves wfireleaves added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 15, 2020
@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 Jul 15, 2020
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3799 for more discussion.

/dup #3799

@ghost
Copy link

ghost commented Jul 15, 2020

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 Jul 15, 2020
@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 Jul 15, 2020
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