Skip to content

Custom triggers #145

Closed
Closed

Description

@gagata

Is your feature request related to a problem? Please describe.

Requested on Discord by zouhir

Describe the solution you'd like?

what are custom triggers?
allow users to define some regular expression and when matched in a command output, trigger an action. Example:
- if matched '^ERROR.*' -> highlight red.
- if matched ^https?:// -> make clickable link

Additional context

iTerm2 triggers & supported actions

Activity

  1. changed the title [-]Custom triggers[/-] [+]Idea: Custom triggers[/+] on Nov 7, 2021
  2. changed the title [-]Idea: Custom triggers[/-] [+]Plugin: Custom triggers[/+] on Nov 8, 2021
  3. changed the title [-]Plugin: Custom triggers[/-] [+]Custom triggers[/+] on Dec 7, 2021
  4. mds1 commented on Dec 16, 2021

    @mds1

    +1 on this. The one big thing I miss from iTerm2 is their trigger support, namely:

    • Highlighting text various colors when it matches some regex
    • Having text link to a URL if it matches some regex, where the URL includes the matched string
  5. elviskahoro commented on Jan 3, 2022

    @elviskahoro
    Contributor

    Combining triggers with collapsable blocks +/ compact mode

    only show one line of output, for instance when running yarn add react, for example it would be useful when upgrading from yarn outdated output

    would be great if the output is smart ;) and you can activate it with something like shift+enter

    The way I imagine it is that all output is squashed into one line with an ability to expand (or scroll).
    It really depends on your current workflow in the terminal. Some commands, like code generation or package installation give a whole bunch of lines of output while the only thing I need to know is "success" or "failure". It's nice to have the blocks as a history without having to scroll a whole bunch.

  6. elviskahoro commented on Jan 5, 2022

    @elviskahoro
    Contributor

    image

  7. locked and limited conversation to collaborators on Jan 20, 2022
  8. converted this issue into a discussion #630 on Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions