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

Cmd/Bash input command macros #5308

Closed
suchislife801 opened this issue Apr 10, 2020 · 2 comments
Closed

Cmd/Bash input command macros #5308

suchislife801 opened this issue Apr 10, 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

@suchislife801
Copy link

Cmd/Bash input command macros

Proposed technical implementation details

  • A method for allowing the clicking of user dynamically created buttons to call macros that contain cmd/bash commands in their native form.

For example

a. When a user is on Windows under a cmd tab, the button1_Click event could...

Windows

button1_Click event = dir
Action = list directory contents.

b. When a user is on Linux under a bash tab, the button_Click event could...

Linux

button2_Click event = ls
Action = list directory contents.

A clear and concise description of what you want to happen.

  • In the process of creating a button, the user assigns a macro to it. A macro is nothing more then a string of native commands that already exist in their own respective operating systems.

  • The buttons would have a property propTargetSystem & propIssueCommand that would allow the user to target each macro created to their respective operating system.

  • Alternatively, this could be possibly implemented as a "Favorites" dropdown menu.

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

Okay so this is kinda similar to #5273. There's also #2046, which could be combined with #a-shortcut-action-for-sending-input (I can't find the issue ATM) might be able to achieve this.

Since this is so similar, I think I'm just going to resolve it as a dupe. Thanks!

/dup #5273

@ghost
Copy link

ghost commented Apr 10, 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 Apr 10, 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 Apr 10, 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