You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
Activity
[-]Custom triggers[/-][+]Idea: Custom triggers[/+][-]Idea: Custom triggers[/-][+]Plugin: Custom triggers[/+][-]Plugin: Custom triggers[/-][+]Custom triggers[/+]mds1 commentedon Dec 16, 2021
+1 on this. The one big thing I miss from iTerm2 is their trigger support, namely:
elviskahoro commentedon Jan 3, 2022
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.
elviskahoro commentedon Jan 5, 2022