Triggers(Including Text Strings) and Actions (internal or external calls)

[fischerdouglas]

Description of the new feature/enhancement

A Trigger system that will monitor several types o events, including text strings on the screen, that will be able to call several types of actions, like scripts, commands, or any resources possible of Windows Terminal.

Proposed technical implementation details (optional)

"Nothing is created, everything is copied."
As you you may see, I'm a fan of iTerm2, my buddy for several years.
But I like this new Microsoft Style, so I'm trying to help.

The Suggestion her is a bit bold.
Provide an complementar Framework that will allow user execute almost any possible predefined action based on almost any event on the Windows Terminal.

A sub-system the will be monitoring events, and if it matches with some pre-activated event, it will trigger the action.

The triggers could be a simple match with a string on the text, or even something like an server-ended-session if it was an SSH/Telnet connection.

The actions could be the automatic highlight of the text, a long beep, open a new tab, or call an external app passing some parameters and receiving back some answer.

---

As I'm not a developer, and also not good with descriptions like these, I will bring the description of this Feature in iTerm2:
https://www.iterm2.com/documentation-one-page.html#documentation-triggers.html

[WSLUser]

This sounds like a dupe of some other issue dealing with clickable links and scripts...a great extension idea though if it's done like it is in Iterm2.

[zadjii-msft]

x-linking with #12366.

Maybe it needs to be closer to

"triggers": [
    { 
        "type": "matchRegex",
        "match": "    git push --set-upstream origin (.*)",
        "command": { "action": "sendInput", "input": "git push --set-upstream origin ${match[0]}" }
    }
]

---

From iterm2 docs

Triggers have a regular expression, an action, an optional parameter, and may be marked as Instant

so that would cover

• a regular expression
• an action
• I believe the ${match[0]} thing I have there is vaguely the "optional parameter" thing
• "Instant" seems easy enough as a bool, though I'd probably want to play with it in iterm2 to get a more precise feel

---

<hackathon thoughts>
These actions would need to be stored as raw json and then evaluated when we want to swap out the ${match[0]} bits. That's probably annoyingly painful perf wise. We'd also need to like, pass the regexes as indexes to the Control, who then raises an event saying "regex 1 happened". Awkward. Plus there's the whole JSON escaping problem then, don't want the match exiting the json string.

But, there's also the concept of the right-click context menu that likely needs to evaluate the actions json when the right click happens, to populate entries accordingly. I suppose these would come with caveats that "using many triggers may substantially impact performance"