Allow setting standard input #46
Comments
|
Support from termux-app side was already added in Limits for intents and command line arguments are few hundred KB and similar as mentioned in Arguments and Result Data Limits but may even be lower for intents as per termux/termux-app@f62febb. So best not pass too much data. Moreover, storing large amounts of data in tasks/variables is gonna cause problems in Tasker, including crashes. |
agnostic-apollo
added a commit
to agnostic-apollo/termux-tasker
that referenced
this issue
Sep 11, 2021
…sign plugin configuring views Users can now pass scripts via `stdin`, like a `bash` script to the `$PREFIX/bin/bash` shell and a `python` script to the `$PREFIX/bin/python` shell or any other commands. Note that if passing script via `stdin`, do not pass arguments, since it will fail depending on shell, at least will for `bash`. Max length of script supported is `45K` characters as per Tasker plugin bundle limits, check `EditConfigurationActivity.setStdinView()` for details. The plugin configuring screen has been redesigned with `CardView` support. For `stdin`, the `TextIOActivity` provided by `termux-shared` will be used. The `strings.xml` naming convention has been updated. Closes termux#46
|
Closed by 05af1af |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature description
I think it would be useful to be set
stdinfor the command. This would allow a bit more data to be passed to the command, with less concern about escaping.The text was updated successfully, but these errors were encountered: