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
I think it would increase usability if arguments could be passed to shell scripts using environmental or contextual variables.
Example:
If the user selects file(s) in Finder, the file(s) paths can be passed as arguments to an inline or path based script.
If we add support for passing of arguments, you could take it one step further and have one command produce output for the succeeding command(s). That could open up for command chains and ability to produce unique command type(s) that can take output.
Example:
Output from a script command is sent to an AnnounceCommand which has different types, either by using say command or notification center to render the result of the script execution result.
The text was updated successfully, but these errors were encountered:
I think it would increase usability if arguments could be passed to shell scripts using environmental or contextual variables.
Example:
If we add support for passing of arguments, you could take it one step further and have one command produce output for the succeeding command(s). That could open up for command chains and ability to produce unique command type(s) that can take output.
Example:
The text was updated successfully, but these errors were encountered: