tudo
is a wrapper script to drop to any supported shell or execute shell script files or their text passed as an argument with termux
user context in Termux App. Check the Usage and Command Types sections for more info on what type of commands can be run. tudo
stands for termux user do.
Make sure to read the Worthy Of Note section, specially the RC File Variables section. This is very important.
To use tudo
with Termux:Tasker plugin and RUN_COMMAND Intent, check Termux:Tasker Setup Instructions
section for details on how to them up. The Tasker App or your plugin host app must be granted com.termux.permission.RUN_COMMAND
permission. The tudo
script must be installed at $PREFIX/bin/tudo
. The allow-external-apps
property must also be set to true
in ~/.termux/termux.properties
file since the $PREFIX/bin/tudo
absolute path is outside the ~/.termux/tasker/
directory. For android >= 10
, the Termux App should also be granted Draw Over Apps
permission so that foreground commands automatically start executing without the user having to manually click the Termux
notification in the status bar dropdown notifications list for the commands to start. Check Templates section for template tasks that can be run used to run tudo
from Termux:Tasker
plugin and RUN_COMMAND Intent
.
If you want to run commands in superuser (root)
user context, check sudo.
- Dependencies
- Downloads
- Install Instructions For Termux In Android
- Current Features
- Planned Features
- Usage
- Command Types
- Supported Shells
- Command Options
- Shell Home
- Shell RC Files
- Shell History Files
- Modifying Default Values
- Examples
- Templates
- Passing Arguments
- Issues
- Worthy Of Note
- Tests
- FAQs And FUQs
- Changelog
- Contributions
- Credits
- Donations
Using tudo
directly from inside termux
terminal session does not have any specific version requirements, other than bash
version >= 4.1
.
However, to use tudo
with Termux:Tasker plugin and RUN_COMMAND Intent requires the following versions to be installed. Check Passing Arguments section and Termux:Tasker Setup Instructions
section for details.
- Termux App version
>= 0.100
- Tasker App version
>= 5.9.4.beta
- Termux:Tasker version
>= 0.5
Latest version is v0.1.0
.
The tudo
file should be placed in termux bin
directory /data/data/com.termux/files/usr/bin
.
It should have termux
uid:gid
ownership and have executable 700
permission before it can be run directly without bash
.
-
Download the
tudo
file.-
Download to termux bin directory directly from github using
curl
using a non-root termux shell.
Runpkg install curl
to installcurl
first.-
Latest release:
curl -L 'https://github.com/agnostic-apollo/tudo/releases/latest/download/tudo' -o "/data/data/com.termux/files/usr/bin/tudo"
-
Specific release:
curl -L 'https://github.com/agnostic-apollo/tudo/releases/download/v0.1.0/tudo' -o "/data/data/com.termux/files/usr/bin/tudo"
-
Master Branch may be unstable:
curl -L 'https://github.com/agnostic-apollo/tudo/raw/master/tudo' -o "/data/data/com.termux/files/usr/bin/tudo"
-
-
Download
tudo
file manually from github to the android download directory and then copy it to termux bin directory.You can download the
tudo
file from a github release from theAssets
dropdown menu.You can also download it from a specific github branch/tag by opening the
tudo
file from theCode
section.
Right-click or hold theRaw
button at the top and selectDownload/Save link
.Then copy the file to termux bin directory using
cat
command below or use a root file browser to manually place it.cat "/storage/emulated/0/Download/tudo" > "/data/data/com.termux/files/usr/bin/tudo"
-
-
Set
termux
ownership and executable permissions.-
If you used a
curl
orcat
to copy the file, then use a non-root termux shell to set ownership and permissions withchown
andchmod
commands respectively:export termux_bin_path="/data/data/com.termux/files/usr/bin"; export owner="$(stat -c "%u" "$termux_bin_path")"; chown "$owner:$owner" "$termux_bin_path/tudo" && chmod 700 "$termux_bin_path/tudo";
-
If you used a root file browser to copy the file, then use
su
to start a root shell to set ownership and permissions withchown
andchmod
commands respectively:export termux_bin_path="/data/data/com.termux/files/usr/bin"; export owner="$(stat -c "%u" "$termux_bin_path")"; su -c "chown \"$owner:$owner\" \"$termux_bin_path/tudo\" && chmod 700 \"$termux_bin_path/tudo\"";
-
Or manually set them with your root file browser. You can find
termux
uid
andgid
by running the commandid -u
in a non-root termux shell or by checking the properties of the termuxbin
directory from your root file browser.
-
- Allows dropping to an interactive shell in
termux
user context for any of the supported Interactive Shells with priority to either termux or android binary and library paths. - Allows running single commands in
termux
user context without having to start an interactive shell including commands in/system
partition. - Allows passing of script file paths or script text as arguments for any of the supported Script Shells to have them executed in
termux
user context without having to create physical script files first for the later case, like in~/.termux/tasker/
directory for Termux:Tasker. - Automatic setup of home directories,
rc
files,history
files and working directories with proper ownership and permissions. - Automatic setup of the shell environment and exporting of all required variables including
LD_PRELOAD
so that termux commands work properly, specifically if being run from Termux:Tasker or RUN_COMMAND Intent. - Provides a lot of Command Options that are specifically designed for usage with Termux:Tasker and the RUN_COMMAND Intent.
-
tudo is a wrapper script to drop to the supported shells or execute
shell script files or their text passed as an argument with termux
user context in termux.
Usage:
tudo [command_options] su
tudo [command_options] asu
tudo [command_options] [-p] <command> [command_args]
tudo [command_options] -s <core_script> [core_script_args]
Available command_options:
[ -h | --help ] display this help screen
[ --help-extra ] display more help about how tudo command works
[ --version ] display version
[ -v | -vv ] set verbose level to 1 or 2
[ -a ] force set priority to android paths for path
command type
[ -b ] go back to last activity after running core_script
[ -B ] run core_script in background
[ -c ] clear shell after running core_script
[ -d ] disable stdin for core_script
[ -e ] exit early if core_script fails
[ -E ] exec interactive shell or the path command
[ -f ] force use temp script file for core_script
[ -F ] consider core_script to be a path to script file
instead of script text
[ -H ] same tudo post shell home as tudo shell home
[ -i ] run interactive tudo post shell after running
core_script
[ -l ] go to launcher activtiy after running core_script
[ -L ] export all existing paths in '$LD_LIBRARY_PATH'
variable
[ -n ] redirect stderr to /dev/null for core_script
[ -N ] redirect stdout and stderr to /dev/null for
core_script
[ -o ] redirect stderr to stdout for core_script
[ -O ] redirect stdout to stderr for core_script
[ -p ] set 'path' as command type [default]
[ -P ] export all existing paths in '$PATH' variable
[ -r ] parse commands as per RUN_COMMAND intent rules
[ -s ] set 'script' as command type
[ -S ] same tudo post shell as tudo shell
[ --comma-alternative=<alternative> ]
comma alternative character to be used for
the `-r` option instead of the default
[ --dry-run ]
do not execute tudo commands
[ --export-paths=<paths> ]
additional paths to export in PATH variable,
separated with colons ':'
[ --export-ld-lib-paths=<paths> ]
additional paths to export in LD_LIBRARY_PATH
variable, separated with colons ':'
[ --hold[=<string>] ]
hold tudo from exiting until string is entered,
defaults to any character if string is not passed
[ --hold-if-fail ]
if '--hold' option is passed, then only hold if
exit code of tudo does not equal '0'
[ --list-interactive-shells ]
display list of supported interactive shells
[ --list-script-shells ]
display list of supported script shells
[ --no-create-rc ]
do not create rc files automatically
[ --no-create-hist ]
do not create history files automatically
[ --no-hist ]
do not save history for tudo shell and tudo post
shell
[ --no-log-args ]
do not log arguments and core_script content
when verbose mode is enabled
[ --keep-temp ]
do not delete tudo temp directory on exit
[ --post-shell=<shell> ]
name or absolute path for tudo post shell
[ --post-shell-home=<path> ]
absolute path for tudo post shell home
[ --post-shell-options=<options> ]
additional options to pass to tudo post shell
[ --post-shell-post-commands=<commands> ]
bash commands to run after tudo post shell
[ --post-shell-pre-commands=<commands> ]
bash commands to run before tudo post shell
[ --post-shell-stdin-string=<string> ]
string to pass as stdin to tudo post shell
[ --remove-prev-temp ]
remove temp files and directories created on
previous runs of tudo command
[ --script-decode ]
consider the core_script as base64
encoded that should be decoded before execution
[ --script-name=<name> ]
filename to use for the core_script temp file
created in '.tudo.temp.XXXXXX' directory instead
of 'tudo_core_script'
[ --script-redirect=<mode/string> ]
core_script redirect mode for stdout and stderr
[ --shell=<shell> ]
name or absolute path for tudo shell
[ --shell-home=<path> ]
absolute path for tudo shell home
[ --shell-options=<options> ]
additional options to pass to tudo shell
[ --shell-post-commands=<commands> ]
bash commands to run after tudo shell for script
command type
[ --shell-pre-commands=<commands> ]
bash commands to run before tudo shell
[ --shell-stdin-string=<string> ]
string to pass as stdin to tudo shell for script
command type
[ --sleep=<seconds> ]
sleep for x seconds before exiting tudo
[ --sleep-if-fail ]
if '--sleep' option is passed, then only sleep if
exit code of tudo does not equal '0'
[ --title=<title> ]
title for tudo shell terminal
[ --work-dir=<path> ]
absolute path for working directory
Set verbose level to 1 or 2 to get more info when running tudo command.
Pass '--dry-run' option with verbose mode enabled to see the commands
that will be run without actually executing them.
Visit https://github.com/agnostic-apollo/tudo for more help on how
tudo command works.
The 'su' command type drops to a termux user interactive
shell for any of the supported interactive shells. To drop to a
'bash' shell, just run 'tudo su'. The priority will be set to termux
bin and library paths in '$PATH' and '$LD_LIBRARY_PATH' variables.
Use the '--shell' option to set the interactive shell to use.
The 'asu' command type is the same as 'su' command type but
instead the priority will be set to android bin and library paths in
'$PATH' and '$LD_LIBRARY_PATH' variables.
Use the '--shell' option to set the interactive shell to use.
The 'path' command type runs a single command in termux user
context. You can use it just by running 'tudo <command> [command_args]'
where 'command' is the executable you want to run and 'command_args'
are any optional arguments to it. The 'command' will be run within a
'bash' shell. Priority is given to termux bin and library paths unless
'command' exists in '/system' partition.
The 'script' command type takes any script text or path to a script
file for any of the supported script shells referred as 'tudo shell',
and executes the script with any optional arguments with the desired
script shell. This can be done by running the
'tudo -s <core_script> [core_script_args]' command.
The 'core_script' will be considered a 'bash' script by default.
The 'core_script' will be passed to the desired shell using
process substitution or after storing the 'core_script' in a temp file
in a temp directory in 'tudo shell' home
'$TMPDIR/.tudo.temp.XXXXXX/tudo_core_script' and passing the path to
the desired shell, where 'XXXXXX' is a randomly generated string.
The method is automatically chosen based on the script shell
capabilities. The '-f' option can be used to force the usage of a
script file. The '-F' option can passed so that the 'core_script'
is considered as a path to script file that should be passed to
'tudo shell' directly instead of considering it as a script text.
Use the '--shell' option to set the script shell to use.
Use the '--post-shell' option to set the interactive shell to use if
'-i' option is passed.
Run "exit" command of your shell to exit interactive shells and return
to the termux shell.
The su
command type drops to an interactive shell with termux
user context for any of the supported Interactive Shells. su
stands for substitute user which in this case will be the termux
user. To drop to a bash
shell, just run tudo su
. The priority will be set to termux bin and library paths in $PATH
and $LD_LIBRARY_PATH
variables. Check the PATH and LD_LIBRARY_PATH Priorities section for more info.
If you just use start the Termux App to start a foreground terminal session to run termux
commands, then this command type may not be too useful, especially for usage with bash
since termux
user being used would be the same as the default. However, you can use this command type to start an interactive shell session for different shells from plugins. tudo
will also automatically create the rc
and history
files for the shell.
Note that su
is just a command type and does not represent the su
binary itself. Use the path
command type to run the tudo -p su [user]
command instead for calling the su
binary.
The asu
command type is the same as su
command type but instead the priority will be set to android bin and library paths in $PATH
and $LD_LIBRARY_PATH
variables. Check the PATH and LD_LIBRARY_PATH Priorities section for more info.
This can also be useful to run commands in /system
partition since termux does not automatically export those paths in $PATH
and $LD_LIBRARY_PATH
and you would normally get command not found
errors if you attempt to run them.
The path
command type runs a single command in termux
user context. You can use it just by running tudo <command> [command_args]
where command
is the executable you want to run and command_args
are any optional arguments you want to pass to it.
The command
will be run within a bash
shell. Priority is given to termux bin and library paths unless command
exists in /system
partition. tudo <command>
will not work if executable to be run does not have proper ownership or executable permissions set that disallows termux
user to read or execute it if tudo
command itself is being run from the termux
context. The command
must be an absolute path
to an executable, or basename
to an executable in the current directory or in a directory listed in the final $PATH
variable that is to be exported by the tudo
command. If it is not found, tudo
will exit with an error.
The path
command type can be useful for running single commands in /system
partition that require priorities to be set to android library paths and which fail otherwise with errors like CANNOT LINK EXECUTABLE
and cannot locate symbol some_symbol referenced by /lib....
. The tudo
command will automatically detect if the command
exists in /system
partition and set priorities to android bin and library paths in $PATH
and $LD_LIBRARY_PATH
variables. So running tudo logcat
will just work. You can also force setting priority to android paths by passing the -a
option or to run a binary in /system
partition instead of that in termux bin paths.
You can also use tudo <command>
even if you are inside of a tudo su
shell and it will work without having to switch to tudo asu
or exporting variables to change priority.
You can also run the tudo -p su [user]
or tudo -p /path/to/su [user]
commands to call the su
binary for dropping to a shell for a specific user or even run a command for a specific user, like tudo -p su -c "logcat" system
. Note that if you do not provide an absolute path to the su
binary and just run tudo -p su
, then the termux su
wrapper script will be called which is stored at $PREFIX/bin/su
which automatically tries to find the su
binary and unsets LD_LIBRARY_PATH
and LD_PRELOAD
variables. You can check its contents with cat "$PREFIX/bin/su"
. The variables will be also be unset by the tudo
script if it detects you are trying to run a su
binary. The device must of course be rooted and ideally Termux
must have been granted root permissions by your root manager app like SuperSU or Magisk for the su
commands to work. However, it is highly advised that you use sudo instead of [tudo] for calling the su
binary so that it sets a different home than the termux home used by tudo
by default, among other things.
Check the -a
and -r
command options that can be specifically used with the path
command type.
The script
command type takes any script text or path to a script file for any of the supported Script Shells referred as tudo shell
, and executes the script with any optional arguments with the desired script shell. This can be done by running the tudo -s <core_script> [core_script_args]
command. The core_script
will be considered a bash
script by default.
The script
command type is incredibly useful for usage with termux plugins like Termux:Tasker or RUN_COMMAND Intent. Currently, any script files that need to be run need to be created in ~/.termux/tasker/
directory, at least for Termux:Tasker
. It may get inconvenient to create physical script files for each type of command you want to run. These script files are also neither part of backups of plugin host apps like Tasker and require separate backup methods and nor are part of project configs shared with other people or even between your own devices, and so the scripts need to be added manually to the ~/.termux/tasker/
directory on each device. To solve such issues and to dynamically define scripts of different interpreted languages inside your plugin host app like Tasker
in local variables (all lowercase %core_script
) of a task and to pass them to Termux
as arguments instead of creating script files, the script
command type can be used. The termux environment will also be properly loaded like setting LD_PRELOAD
etc before running the commands.
The core_script
will be passed to the desired shell using Process Substitution or after storing the core_script
in a temp file in a temp directory in $TMPDIR/.tudo.temp.XXXXXX/tudo_core_script
and passing the path to the desired shell, where XXXXXX
is a randomly generated string. The method is automatically chosen based on the script shell capabilities. The -f
option can be used to force the usage of a script file. If the temp directory is created, it will be empty other than the tudo_core_script
file and will be unique for each execution of the script, which the script can use for other temporary stuff without having to worry about cleanup since the temp directory will be automatically removed when tudo
command exits unless --keep-temp
is passed. The temp directory path will also be exported in the $TUDO_SCRIPT_DIR
environment variable which can be used by the core_script
, post shell
and --*shell-*-commands
options, like --shell-pre-commands='cd "$TUDO_SCRIPT_DIR"'
. The $TMPDIR
refers to /data/data/com.termux/files/usr/tmp
which the tmp
directory path for the Termux
app.
For bash zsh fish ksh python python2 ruby perl lua5.2 lua5.3 lua5.4
, process substitution is used by default and for dash sh node php
a file is used. If the usage of process substitution is breaking for some complex scripts of some specific shell, please report the issue.
The -F
option can be passed so that the core_script
is considered as a path to a script file that should be passed to tudo shell
directly instead of considering it as a script text.
The core_script
can optionally not be passed or passed as an empty string so that other "features" of the script
command type can still be used without calling the script shell.
It may also be important to automatically open an interactive shell after the core_script
completes. This can be done by using the -i
option along with --post-shell*
options. The tudo post shell
can be any of the supported Interactive Shells and defaults to bash
. The same shell as the script tudo shell
can also be used for tudo post shell
by passing the -S
option as long as the tudo shell
exists in the list of supported interactive shells. The environment variable $TUDO_SCRIPT_EXIT_CODE
will be exported containing the exit code of the core_script
before the interactive shell is started. Running an interactive shell will also keep the terminal session open after commands complete which is normally closed automatically when commands are run with the plugin or intents, although the --hold
option can also be used for this.
You can define your own exit traps inside the core_script
, but DO NOT define them outside it with the --*shell-*-commands
options since tudo
defines its own trap function tudo_script_trap
for cleanup, killing child processes and to exit with the trap signal exit code. If you want to handle traps outside the core_script
, then define a function named tudo_script_custom_trap
which will automatically be called by tudo_script_trap
. The function will be sent TERM
, INT
, HUP
, QUIT
as $1
for the respective trap signals. For the EXIT
signal the $1
will not be passed. Do not exit
inside the tudo_script_custom_trap
function. If the tudo_script_custom_trap
function exits with exit code 0
, then the tudo_script_trap
will continue to exit with the original trap signal exit code. If it exits with exit code 125
ECANCELED
, then tudo_script_trap
will consider that as a cancellation and will just return without running any other trap commands. If any other exit code is returned, then the tudo_script_trap
will use that as exit code instead of the original trap signal exit code.
Check the -b
, -B
, -c
, -d
, -e
, -E
, -f
, -F
, -l
, -n
, N
, -o
, O
, -r
, --remove-prev-temp
, --keep-temp
, --shell*
, --post-shell*
, --script-decode
, --script-redirect
, --script-name
command options that can be specifically used with the script
command type.
The bash
shell is the default interactive and script shell and must exist at $PREFIX/bin/bash
with ownership and permissions allowing termux
user to read and execute it. The --shell
and --post-shell
options can be used to change the default shells. The path
command type always uses the bash
shell and command options are ignored. The shells must have proper ownership or executable permissions set that allows termux
user to read and execute them.
The exported environmental variables $TUDO_SHELL_PS1
and $TUDO_POST_SHELL_PS1
can be used to change the default $PS1
values of the shell, provided that the shell uses it. Check the Modifying Default Values section for more info on tudo
environmental variables and modifying default values.
The supported interactive shells are: bash zsh dash sh fish python ruby pry node perl lua5.2 lua5.3 lua5.4 php python2 ksh
These shells can be used for the su
and asu
command types like tudo --shell=<shell> su
and tudo --shell=<shell> asu
and also as post shell for script
command type when the -i
option is passed like tudo -si --post-shell=<shell> <core_script>
to start an interactive shell after script commands complete.
The bash
shell is automatically chosen as the default interactive shell if the --shell
or --post-shell
options are not passed to set a specific shell. You can pass the name of a shell listed in the supported shells list like --shell=zsh
or an absolute path like --shell=/path/to/zsh
. The $PREFIX/
and ~/
prefixes are also supported, like $PREFIX/bin/zsh
or ~/zsh
.
For perl
, the interactive shell is started using rlwrap
, which must be installed. Use pkg install rlwrap
to install.
The supported script shells are: bash zsh dash sh fish python ruby node perl lua5.2 lua5.3 lua5.4 php python2 ksh
These shells can be used for the script
command type like tudo -s --shell=<shell> <core_script>
.
The bash
shell is automatically chosen as the default script shell if the --shell
option is not passed to set a specific shell. You can pass the name of a shell listed in the supported shells list like --shell=zsh
or an absolute path like --shell=/path/to/zsh
. The $PREFIX/
and ~/
prefixes are also supported, like $PREFIX/bin/zsh
or ~/zsh
.
The $PREFIX/
and ~/
prefixes are supported for all command options that take in absolute paths as arguments. The $PREFIX/
is a shortcut for the termux prefix directory /data/data/com.termux/files/usr/
. The ~/
is a shortcut for the termux home directory /data/data/com.termux/files/home/
. Note that if the paths with shortcuts are not surrounded with single quotes, they will expanded by the local shell before being passed to the tudo
script instead of the tudo
script manually expanding them. Note that ~/
will expand to the shell or post shell home and not the necessarily the termux home if used inside scripts or the *-commands
options.
It's the users responsibility to properly quote all arguments passed to command options and also for any values like paths passed inside the arguments, specifically the *-commands
and *-options
options, so that whitespace splitting does not occur.
Check Arguments and Result Data Limits for details on the max size of arguments that you can pass to tudo
script, specifically the size of core_script
and its arguments for the script
command type.
-
-v | -vv
options can be used to increase the verbose level of thetudo
command. Useful to see script progress and what commands will actually be run. You can also use verbose mode with the--dry-run
option to see what commands will be run without actually executing them. -
-a
option can be used with thepath
command type to force setting priority to android bin and library paths in$PATH
and$LD_LIBRARY_PATH
variables. This can be useful for cases when thecommand
is an absolute path but does not exist in the/system
partition but still needs priority to be set to android paths or if thecommand
is a just the basename and you want to run the binary in/system
partition instead of the one in termux bin path since that will be found first during the search since the$PATH
variable will be set to priority to android paths. -
-b
option can be used with thescript
command type mainly for when commands are to be run in a foreground terminal session from plugins. This will simulate double back button press once thecore_script
is complete to go to the last activity, first to close keyboard and second to close terminal session. Use this only for short scripts, otherwise the user may have switched from the terminal session to a different app and back buttons simulation would be done inside that app instead. -
-B
option can be used with thescript
command type to run thecore_script
in background with&
(not the entiretudo
command). This can be used with the-i
option or even with the--shell-post-commands
option. Thepid
of the background process will be available in the$TUDO_SCRIPT_PID
variable. Note that all child processes are killed whentudo
exits. -
-c
option can be used with thescript
command type mainly for when commands are to be run in a foreground terminal session from plugins and an interactive shell session needs to be opened after thecore_script
is complete with the-i
option. This will clear the terminal session once thecore_script
is complete. -
-d
option can be used with thescript
command type to disablestdin
for thecore_script
. This will redirect thestdin
to/dev/null
and unset the$PS1
variable so that thecore_script
can detect that thestdin
is not available and run the script in a non-interactive mode. If thecore_script
doesn't check ifstdin
is available or not and still attempts to read, it will receive nothing as input or may even cause exceptions in some script shells ifI/O
exceptions are not handled properly. Note that when plugin commands are run in a foreground terminal session, then even though keyboard is not shown,stdin
is available and can be requested by the script which will then open the keyboard. -
-e
option can be used with thescript
command type to exit early ifcore_script
fails due to an exit code other than0
without running any commands meant to be run after thecore_script
like defined by-b
,-c
,-i
,-l
,--post-shell-pre-commands
and--post-shell-options
command options. If-B
is passed, then this is ignored. -
-E
option can be used toexec
thesu
that runs the finaltudo
command_type
command. The commands for--hold
and--sleep
options and any other commands that need to be run after thetudo
command_type
command will not be run. -
-f
option can be used with thescript
command to force usage of$TMPDIR/.tudo.temp.XXXXXX/tudo_core_script
temp file for storingcore_script
for debugging or if for reason the shell variant doesn't support process substitution and thetudo
command is automatically trying to use it and is failing. It can also be used to provide a unique temp directory that can be used by thecore_script
which will automatically be deleted after execution. -
-F
option can be used with thescript
command to considercore_script
as a path to script file that should be passed totudo shell
directly instead of considering it as a script text. -
-H
option can be used with thescript
command type with the-i
option to use the same interactivetudo post shell
home as the scripttudo shell
home. This is useful for situations like if you are passing a custom path fortudo shell
home and want to use the same fortudo post shell
home instead of the default home used by thetudo
script. So instead of runningtudo -si --shell-home=/path/to/home --post-shell-home=/path/to/home <core_script>
, you can simple runtudo -siH --shell-home=/path/to/home <core_script>
. -
-i
option can be used with thescript
command to open an interactive shell after thecore_script
completes, optionally specified by--post-shell
option. If the--post-shell
option is not passed, then the shell defaults tobash
. -
-l
option can be used with thescript
command type mainly for when commands are to be run in a foreground terminal session from plugins. This will simulate home button press once thecore_script
is complete to go to the launcher activity. -
-L
option will export all the additional paths that already exist in the$LD_LIBRARY_PATH
variable at the momenttudo
command is run while running shells, The default paths exported bytudo
command will still be exported and prefixed before the additional paths. You can also use the--shell-pre-commands
and--post-shell-pre-commands
options to manually export the$LD_LIBRARY_PATH
variable with a different priority as long as it doesn't break execution of the shells. -
-n
option can be used with thescript
command type to redirectstderr
to/dev/null
only for thecore_script
(not the entiretudo
command). This is a shortcut for--script-redirect=3
. -
-N
option can be used with thescript
command type to redirect bothstdout
andstderr
to/dev/null
only for thecore_script
(not the entiretudo
command). This is a shortcut for--script-redirect=4
. -
-o
option can be used with thescript
command type to redirectstderr
tostdout
only for thecore_script
(not the entiretudo
command). This is a shortcut for--script-redirect=0
. -
-O
option can be used with thescript
command type to redirectstdout
tostderr
only for thecore_script
(not the entiretudo
command). This is a shortcut for--script-redirect=1
. -
-p
option setspath
as the command type fortudo
and is the default command type. -
-P
option will export all the additional paths that already exist in the$PATH
variable at the momenttudo
command is run while running shells, The default paths exported bytudo
command will still be exported and prefixed before the additional paths. You can also use the--shell-pre-commands
and--post-shell-pre-commands
options to manually export the$PATH
variable with a different priority as long as it doesn't break execution of the shells. -
-r
option will parse arguments as perRUN_COMMAND
intent rules. This will by default replace any comma alternate characters‚
(#U+201A
,‚
,‚
,single low-9 quotation mark
) with simple commas,
(U+002C
,,
,,
,comma
) found in anycommand_args
for thepath
command type and incore_script
and anycore_script_args
for thescript
command type. They will also be replaced in the--hold
,--post-shell-home
,--post-shell-pre-commands
,--post-shell-options
,--shell-home
,--shell-pre-commands
,--shell-post-commands
,--shell-options
,--script-name
,--title
and--work-dir
command options passed after the-r
option, so ideally-r
option should be passed before any of them. You can use a different character that should be replaced using the--comma-alternative
option. Check Passing Arguments Using RUN_COMMAND Intent section for why this is may be required. -
-s
option setsscript
as the command type fortudo
. -
-S
option can be used with thescript
command type with the-i
option to use the same interactivetudo post shell
as the scripttudo shell
as long as thetudo shell
exists in the list of supported interactive shells. This is useful for situations like if you are running apython
script and want to start apython
interactive shell after the script completes instead of the likely defaultbash
shell. So instead of runningtudo -si --shell=python --post-shell=python <core_script>
, you can simple runtudo -siS --shell=python <core_script>
. -
--comma-alternative
option can be used to set the comma alternative character to be used for the-r
option instead of the default. -
--dry-run
option will enable dry running of thetudo
script. This will not execute any commands, nor willrc
files,history
files orworking directory
passed be created. However, thetudo shell
home and$TMPDIR/.tudo.temp.XXXXXX/tudo_core_script
file will still be created iftudo_core_script
file needs to be created. It's advisable to also pass the-v
or-vv
options along with this to see script progress and what commands would actually have been run. Passing--keep-temp
may also be useful. -
--export-paths
option can be used to set the additional paths to export in$PATH
variable, separated with colons:
. The string passed must not start or end with or contain two consecutive colons:
. -
--export-ld-lib-paths
option can be used to set the additional paths to export in$LD_LIBRARY_PATH
variable, separated with colons:
. The string passed must not start or end with or contain two consecutive colons:
. -
--hold[=<string>]
option can be used to maketudo
script hold the terminal and not exit until thestring
is entered. Thestring
can only contain alphanumeric and punctuation characters without newlines specified by[:alnum:]
and[:punct:]
bash regex character classes. If only--hold
is passed, thentudo
will exit after any key is pressed. This is useful for cases wheretudo
is being run in a foreground terminal session, like from plugins and the terminal closes as soon as thetudo
exits, regardless of iftudo
failed or was successful without the user getting a chance to see the output. -
--hold-if-fail
option can be used with the--hold
option to only hold if exit code oftudo
does not equal0
. -
--list-interactive-shells
option can be used to display the list of supported Interactive Shells and exit. -
--list-script-shells
option can be used to display the list of supported Script Shells and exit. -
--no-create-rc
option will disable automatic creation ofrc
files fortudo shell
andtudo post shell
if they are missing. -
--no-create-hist
option will disable automatic creation ofhistory
files fortudo shell
andtudo post shell
if they are missing. -
--no-hist
option will try to disable history loading and saving fortudo shell
andtudo post shell
depending on shell capabilities. Not all interactive shells have history support or of disabling it. The history files will also not be created automatically if they are missing. -
--no-log-args
option can be used with thepath
orscript
command type to disable logging of arguments andcore_script
content when verbose mode is enabled. This is useful in cases where the arguments orcore_script
content is too large and it "hides" the other useful log entries due to terminal session output buffer limitations. -
--keep-temp
option will disable automatic deletion of the tudo temp directory$TMPDIR/.tudo.temp.XXXXXX
on exit. This can be used to debug any temp script files created. -
--post-shell=<shell>
option can be used with thescript
command type to pass the name or absolute path fortudo post shell
to be used with thescript
command type and the-i
option. -
--post-shell-home=<path>
option can be used with thescript
command type to pass an absolute path for thetudo post shell
home that overrides the default value. -
--post-shell-options=<options>
option can be used with thescript
command type to set additional options to pass totudo post shell
while starting an interactive shell. -
--post-shell-post-commands=<commands>
option can be used with thescript
command type to set bash commands to be run after thetudo post shell
exits. -
--post-shell-pre-commands=<commands>
option can be used with thescript
command type to set bash commands to be run before thetudo post shell
is started. The commands are run after the commands that are run for the--shell-post-commands
,-b
,-l
and-c
options. -
--post-shell-stdin-string=<string>
] option can be used with thescript
command type to set the string that should be passed asstdin
to thetudo post shell
using process substitution or herestring depending on shell capabilities. Some shells when run in interactive mode may automatically exit after running the commands received throughstdin
or may not even accept strings fromstdin
. This option is used for automated testing. -
--remove-prev-temp
option can be used with thescript
command type to remove temp files and directories created on previous runs oftudo
command that may have been left behind due totudo
being killed and not cleanly exiting, or Termux crashing or being killed by androidOOM
killer or the phone rebooting. Although, temp files are created in$TMPDIR
which is automatically cleared when termux sessions are closed. -
--script-decode
option can be used with thescript
command type so that thecore_script
passed is considered as abase64
encoded string that should be decoded and stored in temp file. The temp file path is passed to the script shell. This can be useful to pass a script whose normal decoded form contains nonUTF-8
or binary data which if passed directly as an argument may be discarded by the shell if not encoded first since such data cannot be stored in bash variables. If this is passed, then-r
option processing will be ignored for thecore_script
but not for any arguments. -
--script-name
option can be used with thescript
command type to set the filename to use for thecore_script
temp file created in$TMPDIR/.tudo.temp.XXXXXX/tudo_core_script
directory instead oftudo_core_script
. The temp file path is passed to the script shell if-f
or--script-decode
is passed or if the script shell doesn't support process substitution or ifcore_script
passed contained nonUTF-8
or binary data. -
--script-redirect=<mode/string>
option can be used with thescript
command type to set the redirect mode or string forstdout
andstderr
for thecore_script
. The following modes are supported:-
0
redirectstderr
tostdout
. This can be used to receive bothstdout
andstderr
in a synchronized way asstdout
, like in%stdout
variable forTermux:Tasker
plugin for easier processing of result of commands. -
1
redirectstdout
tostderr
. This can be used to receive bothstdout
andstderr
in a synchronized way asstderr
, like in%stderr
variable forTermux:Tasker
plugin for easier processing of result of commands. -
2
redirectstdout
to/dev/null
. This can be used to ignorestdout
output of thecore_script
. -
3
redirectstderr
to/dev/null
. This can be used to ignorestderr
output of thecore_script
. -
4
redirectstdout
andstderr
to/dev/null
. This can be used to ignorestdout
andstderr
output of thecore_script
. -
5
redirectstderr
tostdout
andstdout
tostderr
. This can be used to swapstdout
andstderr
output of thecore_script
. -
6
redirectstderr
tostdout
andstdout
to/dev/null
. This can be used to ignorestdout
and to receivestderr
output asstdout
of thecore_script
. -
*
else it is considered a string that's appended after thecore_script
and its arguments. This can be used for custom redirection, like redirection to a file and possibly used along with the--shell-pre-commands
option if some prep is required.
Note that anything sent to
stdout
andstderr
outside thecore_script
shell will still be sent tostdout
andstderr
and will be received in the%stdout
and%stderr
variables forTermux:Tasker
plugin, so do not ignore them completely while checking for failures. -
-
--shell=<shell>
option can be used to pass the name or absolute path fortudo shell
. Forsu
andasu
command types, this is refers to the interactive shell. Forscript
command type, this refers to script shell that should run thecore_script
. Forpath
command type, this option is ignored. -
--shell-home=<path>
option can be used to pass an absolute path for thetudo shell
home that overrides the default value. -
--shell-options=<options>
option can be used to set additional options to pass totudo shell
. Forsu
andasu
command types, these will be passed while starting an interactive shell. Forscript
command type, these will be passed while starting the script shell that will be used to passed thecore_script
. Forpath
command type, these options are ignored. -
--shell-post-commands=<commands>
option can be used with thescript
command type to set bash commands to be run after thetudo shell
running thecore_script
exits. The commands are run before the commands that are run for the-b
,-l
,-c
and--post-shell-pre-commands
options. -
--shell-pre-commands=<commands>
option can be used to set bash commands to be run before thetudo shell
is started. The commands are run after thecd
command for--work-dir
is run. -
--shell-stdin-string=<string>
] option can be used with thesu
asu
andscript
command type to set the string that should be passed asstdin
to thetudo shell
using process substitution or herestring depending on shell capabilities. Some shells when run in interactive mode may automatically exit after running the commands received throughstdin
or may not even accept strings fromstdin
. This option is used for automated testing. -
--sleep=<seconds>
option can be used to maketudo
script to sleep forx
seconds before exiting. Seconds can be an integer or floating point number that is passed to thesleep
command. This is useful for cases wheretudo
is being run in a foreground terminal session, like from plugins and the terminal closes as soon as thetudo
exits, regardless of iftudo
failed or was successful without the user getting a chance to see the output. -
--sleep-if-fail
option can be used with the--sleep
option to only sleep if exit code oftudo
does not equal0
. -
--title=<title>
option can be used to set the title for the foreground terminal session, that is shown in thetermux
sidebar. -
--work-dir=<path>
option can be used to set the absolute path for working directory for thetudo shell
. Thecd
command is run before the commands passed with--shell-pre-commands
and--post-shell-pre-commands
options are run. The directory will be automatically created if missing.
The default $HOME
directory for tudo shell
and tudo post shell
is termux home /data/data/com.termux/files/home
. The --shell-home
and --post-shell-home
options or the exported environmental variables $TUDO_SHELL_HOME
and $TUDO_POST_SHELL_HOME
can be used to change the default directory. The home directory is the same as termux home directory by default to keep config
, rc
and history
files the same for the termux
user. The home directory should also be owned by the termux
user and have 0700
permission.
Check the Modifying Default Values section for more info on tudo
environmental variables and modifying default values.
The home directory must be under the termux files directory /data/data/com.termux/files/
, and it must not be one of the following directories: ~/.{cache,config,local,termux}
and $PREFIX/*
.
The home directory is automatically created when tudo
command is run if it does not exist. The termux
user ownership and 700
permission is also set to it.
The following shell rc
files are used for different shells depending on if tudo shell
or tudo post shell
home is different from termux home or shared. The rc
files are usually unique for different shells.
-
If the homes are different, then
tudo
shells andtermux
shells will have differentrc
files, stored in their own homes. -
If the homes are shared, then the
tudo
shells andtermux
shells and will share therc
files by default, stored in termux home. -
If the homes are shared, you can set the environmental variables
$tudo_shell_share_rcfiles_and_histfiles
and$tudo_post_shell_share_rcfiles_and_histfiles
to0
so that if the shell supports it, then differentrc
files will be used, stored in termux home. This will only work if the shell has a--rc
param or environmental variable forrc
files, otherwisetudo
shells andtermux
shells will have to share the sameRCFILE
, implied by(shared)
and(hard-coded)
(by the shell) columns.
For shells that do not have rc
files have their columns set to -
.
Shell | RCFILE (different home or shared home with env variable set to 1) |
RCFILE (shared home with env variable not set to 1) |
Set Method |
---|---|---|---|
bash | .bashrc | .tudo_bashrc | --rcfile |
zsh | .zshrc | (shared) | $ZDOTDIR |
dash | .dashrc | .tudo_dashrc | $ENV |
sh | .shrc | .tudo_shrc | $ENV |
fish | .config/fish/config.fish | (shared) | $XDG_CONFIG_HOME |
python | .pythonrc | .tudo_pythonrc | $PYTHONSTARTUP |
ruby | .irbrc | (shared) | (hard-coded) |
pry | .pryrc | (shared) | (hard-coded) |
node | - | - | - |
perl | - | - | - |
lua5.2 | - | - | - |
lua5.3 | - | - | - |
lua5.4 | - | - | - |
php | php.ini | .tudo_php.ini | -c |
python2 | .python2rc | .tudo_python2rc | $PYTHONSTARTUP |
ksh | .kshrc | .tudo_kshrc | $ENV |
The rc
file parent directory is automatically created when tudo
command is run if it does not exist. The termux
user ownership and 700
permission is also set to it.
The rc
file is automatically created when tudo
command is run if it does not exist. The termux
user ownership and 600
permission is also set to it.
The rc
file parent directory and rc
file will not be created automatically if -no-create-rc
is passed.
Check the Modifying Default Values section for more info on how do modify the $tudo_shell_share_rcfiles_and_histfiles
and $tudo_post_shell_share_rcfiles_and_histfiles
default values.
The following shell history
files are used for different shells depending on if tudo shell
or tudo post shell
home is different from termux home or shared. The history
files are usually unique for different shells.
-
If the homes are different, then
tudo
shells andtermux
shells will have differenthistory
files, stored in their own homes. -
If the homes are shared, then the
tudo
shells andtermux
shells and will share thehistory
files by default, stored in termux home. -
If the homes are shared, you can set the environmental variables
$tudo_shell_share_rcfiles_and_histfiles
and$tudo_post_shell_share_rcfiles_and_histfiles
to0
so that if the shell supports it, then differenthistory
files will be used, stored in termux home. This will only work if the shell has an environmental variable forhistory
files, otherwisetudo
shells andtermux
shells will have to share the sameHISTFILE
, implied by(shared)
and(hard-coded)
(by the shell) columns.
For shells that do not have history
files have their columns set to -
. For shells whose history cannot be disabled have their Disable Method
column set to (not possible)
.
For pry
shell, the existing history will still be loaded, but new history will not be saved.
Shell | HISTFILE (different home or shared home with env variable set to 1) |
HISTFILE (shared home with env variable not set to 1) |
Set Method | Disable Method |
---|---|---|---|---|
bash | .bash_history | .tudo_bash_history | $HISTFILE | HISTFILE="/dev/null" |
zsh | .zsh_history | .tudo_zsh_history | $HISTFILE | HISTFILE="/dev/null" |
dash | .dash_history | .tudo_dash_history | $HISTFILE | HISTFILE="/dev/null" |
sh | .sh_history | .tudo_sh_history | $HISTFILE | HISTFILE="/dev/null" |
fish | .local/share/fish/fish_history | .local/share/fish/tudo_fish_history | $fish_history | --private |
python | .python_history | (shared) | (hard-coded) | readline.write_history_file = *None |
ruby | .irb_history | (shared) | (hard-coded) | (not possible) |
pry | .pry_history | (shared) | (hard-coded) | Pry.config.history_save = false |
node | .node_history | .tudo_node_history | $NODE_REPL_HISTORY | NODE_REPL_HISTORY="" |
perl | .perl_history | .tudo_perl_history | rlwrap --history-filename |
--history-filename "/dev/null" |
lua5.2 | - | - | - | - |
lua5.3 | - | - | - | - |
lua5.4 | - | - | - | - |
php | .php_history | (shared) | (hard-coded) | (not possible) |
python2 | - | - | - | - |
ksh | .ksh_history | .tudo_ksh_history | $HISTFILE | HISTFILE="/dev/null" |
The history
file parent directory is automatically created when tudo
command is run if it does not exist. The termux
user ownership and 700
permission is also set to it.
The history
file is automatically created when tudo
command is run if it does not exist. The termux
user ownership and 600
permission is also set to it.
The history
file parent directory and history
file will not be created automatically if -no-create-hist
or --no-hist
is passed.
Check the Modifying Default Values section for more info on how do modify the $tudo_shell_share_rcfiles_and_histfiles
and $tudo_post_shell_share_rcfiles_and_histfiles
default values.
Check the tudo.config file to see the environmental variables that can be used to change the default values. If the tudo.config
file exits at ~/.config/tudo/tudo.config
, then tudo
will automatically source it whenever it is run. It must have termux
user ownership or be readable by it.
You can download it from the master
branch and set it up by running the following commands. If you are on an older version, you may want to extract it from its release instead.
config_directory="/data/data/com.termux/files/home/.config/tudo"
mkdir -p "$config_directory" && \
chmod 700 -R "$config_directory" && \
curl -L 'https://github.com/agnostic-apollo/tudo/raw/master/tudo.config' -o "$config_directory/tudo.config" && \
chmod 600 "$config_directory/tudo.config"
You can use shell
based text editors like nano
, vim
or emacs
to modify the tudo.config
file.
nano "/data/data/com.termux/files/home/.config/tudo/tudo.config"
You can also use GUI
based text editor android apps that support SAF
. Termux provides a Storage Access Framework (SAF) file provider to allow other apps to access its ~/
home directory. However, the $PREFIX/
directory is not accessible to other apps. The QuickEdit or QuickEdit Pro app does support SAF
and can handle large files without crashing, however, it is closed source and its pro version without ads is paid. You can also use Acode editor or Turbo Editor if you want an open source app.
Note that the android default SAF
Document
file picker may not support hidden file or directories like ~/.config
which start with a dot .
, so if you try to use it to open files for a text editor app, then that directory will not show. You can instead create a symlink for ~/.config
at ~/config_sym
so that it is shown. Use ln -s "/data/data/com.termux/files/home/.config" "/data/data/com.termux/files/home/config_sym"
to create it.
If you use the bash
shell in termux terminal session, you can optionally export the environmental variables like $TUDO_SHELL_HOME
and $TUDO_POST_SHELL_HOME
in the ~/.bashrc
file by adding export TUDO_SHELL_HOME="/path/to/home"
and export TUDO_POST_SHELL_HOME="/path/to/home"
lines to it so that they are automatically set whenever you start a terminal session. However, the ~/.bashrc
and rc
files of other shells will not be sourced if you are running commands from Termux:Tasker
or RUN_COMMAND Intent
, and so it is advisable to use the tudo.config
file instead, which will be sourced in all cases, regardless of how tudo
is run.
Note that $TUDO_SHELL_PS1
and $TUDO_POST_SHELL_PS1
values will not work if $PS1
variable is overridden in rc
files in $PREFIX/etc/
or in tudo shell
and tudo post shell
homes. Check RC File Variables section for more details.
If you are using a foreground terminal session, then you must disable the bash
command completion and history expansion for the current terminal session before running tudo
commands to pass multi-line arguments by running bind 'set disable-completion on'; set +H
. Otherwise bash
will try to auto complete commands and search the history, and you will get prompts like Display all x possibilities? (y or n)
.
- Drop to an interactive
bash
shell intermux
user context with priority set to termux bin and library paths with the default configuration.
tudo su
- Drop to an interactive
python
shell intermux
user context with priority set to termux bin and library paths.
tudo --shell=python --work-dir="~/" su
- Drop to an interactive
bash
shell intermux
user context with priority set to termux bin and library paths with/.tudo
directory astudo shell
home.
tudo --shell-home="/.tudo" su
- Drop to an interactive
bash
shell intermux
user context with priority set to termux bin and library paths with/.tudo
as the shell home and termux home as the working directory. All paths currently in$PATH
and$LD_LIBRARY_PATH
are also exported.
tudo -LP --shell-home="/.tudo" --work-dir='~/' su
- Drop to an interactive
bash
shell intermux
user context with priority set to termux bin and library paths, do not store history, export some additional paths in$PATH
variable, pass additional options to the bash interactive shell starting including a different rc/init file and run some commands before running the bash shell like exporting some variables and running a script. The value of the--shell-options
option is surrounded with double quotes and the--init-file
option value passed in it has double quotes escaped to prevent whitespace splitting when its passed tobash
. The--shell-pre-commands
option is instead surrounded with single quotes as an example and so doesn't need double quotes escaped but will require single quotes in commands to be escaped.
tudo --no-hist --export-paths="/path/to/dir1:/path/to/dir2" --shell-options="--noprofile --init-file \"path/to/file\"" --shell-pre-commands='export VARIABLE_1="VARIABLE_VALUE_1"; export VARIABLE_2="VARIABLE_VALUE_2"; /path/to/script;' su
- Drop to an interactive
bash
shell intermux
user context with priority set to android bin and library paths with the default configuration.
tudo asu
- Run
top
command to show top10
processes of any user.
tudo top -m 10 -n 1
- Run
ps
command to processes of all users.
tudo ps -ef
- Run android
getprop
command to get devicesdk
version.
tudo getprop "ro.build.version.sdk"
- Pass a
bash
script text surrounded with single quotes that prints the first2
args tostdout
. There is normally no need to pass--shell=bash
sincebash
shell would be the default shell.
tudo -s 'echo "Hi, $1 $2."' "bash" "shell"
- Pass a
bash
script text surrounded with single quotes that prints the first2
args tostdout
and start an interactivebash
shell.
tudo -si 'echo "Hi, $1 $2."' "bash" "shell"
- Pass a
bash
script text surrounded with single quotes that prints the first2
args tostdout
and start an interactivebash
shell. The script is forcefully stored in a temp file namedtudo_test
in a temp directory$TMPDIR/.tudo.temp.XXXXXX
, which is also not deleted aftertudo
exits. The title of the terminal session is also set totudo_test
.
tudo -sif --keep-temp --script-name="tudo_test" --title="tudo_test" 'echo "Hi, $1 $2."' "bash" "shell"
- Pass a path to
bash
script file to thebash
shell instead of script text, with2
args and start an interactivebash
shell.
tudo -siF '~/.termux/tasker/termux_tasker_basic_bash_test' "bash" "shell"
- Pass a
bash
script text surrounded with single quotes that prints the first2
args tostdout
and run some commands before running the script like exporting some variables. The--shell-pre-commands
option is surrounded with single quotes and so doesn't need double quotes escaped but will require single quotes in commands to be escaped.
tudo -s --shell-pre-commands='
export VARIABLE_1="VARIABLE_VALUE_1"
export VARIABLE_2="VARIABLE_VALUE_2"
' '
echo "Hi, $1 $2."
echo "VARIABLE_1=\`$VARIABLE_1\`"
echo "VARIABLE_2=\`$VARIABLE_2\`"
' "bash" "shell"
- Pass a
bash
script text surrounded with single quotes that prints the first2
args tostdout
and start an interactivepython
shell and run some commands before running the script, after running the script but before going to launcher activity, and after going to launcher activity but before starting the interactivepython
shell.
tudo -sil --post-shell="python" --shell-pre-commands='echo "Running script"' --shell-post-commands='echo "Script complete\nGoing to launcher"' --shell-pre-commands='echo "Starting interactive python shell"' 'echo "Hi, $1 $2."' "bash" "shell"
- Pass a
bash
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=bash <(cat <<'TUDO_EOF'
echo 'What is your name?'
read name
echo "Hi, $name."
TUDO_EOF
)
- Pass a
bash
script text surrounded with single quotes that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=bash '
echo "What is your name?"
read name
echo "Hi, $name."
'
- Pass a
bash
script text surrounded with single quotes that reads a name fromstdin
and prints it tostdout
, where the script itself also contains single quotes.
tudo -s --shell=bash '
echo '\''What is your name?'\''
read name
echo "Hi, $name."
'
- Pass a
bash
script text with process substitution that prints the first2
args tostdout
and start an interactive shell if only2
args are received, otherwise exits early with an error without starting the interactive shell afterwards. Additional arguments that will be passed to thecore_script
are passed totudo
after the process substitution ends.
tudo -sie --shell=bash <(cat <<'TUDO_EOF'
#if parameter count is not 2
if [ $# -ne 2 ]; then
echo "Invalid parameter count '$#' to 'termux_tasker_basic_bash_test'" 1>&2
echo "$*" 1>&2
exit 1
fi
echo "\$1=\`$1\`"
echo "\$2=\`$2\`"
exit 0
TUDO_EOF
) "hello," "termux!"
- Pass a
bash
script text surrounded with single quotes that redirectsstderr
of thecore_script
tostdout
so that bothstdout
andstderr
can be received in a synchronized way asstdout
, like in%stdout
variable forTermux:Tasker
plugin for easier processing of result of commands.
tudo -so 'echo stdout; echo stderr 1>&2'
- Pass a
bash
script to start thesshd
server and automatically go to launcher activity. The script will also automatically start an interactivebash
shell after starting thesshd
server so thattermux
service andsshd
service keep running in the background because of the permanenttermux
notification, You can run the script fromTermux:Tasker
plugin on device boot, make sureExecute in a terminal session
toggle is enabled. It can also be run with theRUN_COMMAND
intent. (This is how this whole tudo and sudo shit started)
tudo -seli -v --hold --hold-if-fail --title='sshd' '
echo -e "Starting sshd server...\n"
sshd
return_value=$?
if [ $return_value -ne 0 ]; then
echo -e "The sshd server failed to start" 1>&2
exit $return_value
else
echo -e "The sshd server started successfully.\nDo not close this session.\nOtherwise commands over ssh will not work or will get killed while running."
sleep 3
fi
'
- Pass a
zsh
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=zsh <(cat <<'TUDO_EOF'
echo "Hi, $1 $2."
TUDO_EOF
) "zsh" "shell"
- Pass a
zsh
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=zsh <(cat <<'TUDO_EOF'
echo "What is your name?"
read name
echo "Hi, $name."
TUDO_EOF
)
- Pass a
fish
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=fish <(cat <<'TUDO_EOF'
echo "Hi, $argv[1] $argv[2]."
TUDO_EOF
) "fish" "shell"
- Pass a
fish
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=fish <(cat <<'TUDO_EOF'
echo "What is your name?"
read -p "" name
echo "Hi, $name."
TUDO_EOF
)
Currently, python
refers to python3
and python2
refers to python2
in termux. Check Termux Python Wiki for more information.
- Pass a
python
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=python <(cat <<'TUDO_EOF'
import sys
print("Hi, %s %s." % (sys.argv[1], sys.argv[2]))
TUDO_EOF
) "python" "shell"
- Pass a
python
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=python <(cat <<'TUDO_EOF'
name = input("What is your name?\n")
print("Hi, %s." % name)
TUDO_EOF
)
The following "tests" are in solidarity with the youtube-dl
devs, EFF and the current Github response of the "incident".
The youtube-dl
file is actually not a single python script text file but is a binary file containing multiple python files.
- Read
python
script text from a file usingcat
and pass it with process substitution. Passing the data of theyoutube-dl
file totudo
script using process substitution will engage automaticbase64
encoding of the data and creation of temp script file. Theyoutube-dl
generates its help output based on the named of the its own file, hence--script-name
is passed, otherwise help with containtudo_core_script
entries instead. The current size of theyoutube-dl
binary is over1MB
and so its data cannot be passed as an argument directly (afterbase64
encoding) since Arguments Data Limits will cross.
tudo -s --shell=python --script-name="youtube-dl" <(cat "$PREFIX/bin/youtube-dl") --help
- Pass a path to
python
script file to thepython
shell instead of script text, with an arg.
tudo -sF --shell=python '$PREFIX/bin/youtube-dl' --help
- Read
python
script text from a file usingcat
in a subshell and pass it as an argument. The script size must not cross Arguments Data Limits. If the script contains binary or nonUTF-8
data, then pipe the output ofcat
tobase64
and also pass the--script-decode
option.
tudo -s --shell=python "$(cat "$PREFIX/bin/bandcamp-dl")" --help
tudo -s --script-decode --shell=python "$(cat "$PREFIX/bin/bandcamp-dl" | base64)" --help
- Pass a
ruby
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=ruby <(cat <<'TUDO_EOF'
puts "Hi, " + ARGV[0] + " " + ARGV[1] + "."
TUDO_EOF
) "ruby" "shell"
- Pass a
ruby
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=ruby <(cat <<'TUDO_EOF'
puts "What is your name?"
name = STDIN.gets
name = '' if name.nil?
puts "Hi, " + name.chomp.to_s + "."
TUDO_EOF
)
- Pass a
node
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=node <(cat <<'TUDO_EOF'
console.log(`Hi, ${process.argv[2]} ${process.argv[3]}.`)
TUDO_EOF
) "node" "shell"
- Pass a
node
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=node <(cat <<'TUDO_EOF'
const readline = require('readline').createInterface({
input: process.stdin,
output: process.stdout
})
readline.question(`What is your name?\n`, (name) => {
console.log(`Hi, ${name}.`)
readline.close()
})
TUDO_EOF
)
- Pass a
perl
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=perl <(cat <<'TUDO_EOF'
print "Hi, ", $ARGV[0], " ", $ARGV[1], ".\n";
TUDO_EOF
) "perl" "shell"
- Pass a
perl
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=perl <(cat <<'TUDO_EOF'
print "What is your name?\n";
$name = <STDIN>;
chomp($name);
print "Hi, ", $name, ".\n";
TUDO_EOF
)
- Pass a
lua5.2
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=lua5.2 <(cat <<'TUDO_EOF'
io.write('Hi, ', arg[1], ' ', arg[2], '.\n')
TUDO_EOF
) "lua5.2" "shell"
- Pass a
lua5.2
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=lua5.2 <(cat <<'TUDO_EOF'
io.write('What is your name?\n')
local name = io.read()
io.write('Hi, ', name, '.\n')
TUDO_EOF
)
- Pass a
lua5.3
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=lua5.3 <(cat <<'TUDO_EOF'
io.write('Hi, ', arg[1], ' ', arg[2], '.\n')
TUDO_EOF
) "lua5.3" "shell"
- Pass a
lua5.3
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=lua5.3 <(cat <<'TUDO_EOF'
io.write('What is your name?\n')
local name = io.read()
io.write('Hi, ', name, '.\n')
TUDO_EOF
)
- Pass a
lua5.4
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=lua5.4 <(cat <<'TUDO_EOF'
io.write('Hi, ', arg[1], ' ', arg[2], '.\n')
TUDO_EOF
) "lua5.4" "shell"
- Pass a
lua5.4
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=lua5.4 <(cat <<'TUDO_EOF'
io.write('What is your name?\n')
local name = io.read()
io.write('Hi, ', name, '.\n')
TUDO_EOF
)
- Pass a
php
script text with process substitution that prints the first2
args tostdout
.
tudo -s --shell=php <(cat <<'TUDO_EOF'
<?php
echo "Hi, " . $argv[1] . " " . $argv[2] . ".\n";
TUDO_EOF
) "php" "shell"
- Pass a
php
script text with process substitution that reads a name fromstdin
and prints it tostdout
.
tudo -s --shell=php <(cat <<'TUDO_EOF'
<?php
echo "What is your name?\n";
$name = readline();
echo "Hi, " . $name . ".\n";
TUDO_EOF
)
-
Tasks
-
XML
Download the Termux Tasker Plugin Tudo Templates Task XML and Termux RUN_COMMAND Intent Tudo Templates Task XML files to the android download directory. To download, right-click or hold theRaw
button at the top after opening a file link and selectDownload/Save link
or usecurl
from a termux shell. Then import the downloaded task files into Tasker by long pressing theTask
tab button in Tasker home and selectingImport Task
.curl -L 'https://github.com/agnostic-apollo/tudo/raw/master/templates/plugin_hosts/tasker/Termux_Tasker_Plugin_Tudo_Templates.tsk.xml' -o "/storage/emulated/0/Download/Termux_Tasker_Plugin_Tudo_Templates.tsk.xml"
curl -L 'https://github.com/agnostic-apollo/tudo/raw/master/templates/plugin_hosts/tasker/Termux_RUN_COMMAND_Intent_Tudo_Templates.tsk.xml' -o "/storage/emulated/0/Download/Termux_RUN_COMMAND_Intent_Tudo_Templates.tsk.xml"
-
Taskernet
ImportTermux Tasker Plugin Tudo Templates Task
fromTaskernet
from here.
ImportTermux RUN_COMMAND Intent Tudo Templates Task
fromTaskernet
from here.
Check Termux Tasker Plugin Tudo Templates Task Info and Termux RUN_COMMAND Intent Tudo Templates Task Info files for more info on the tasks.
-
Termux needs to be granted Storage
permission to allow it to access /storage/emulated/0/Download
directory, otherwise you will get permission denied errors while running commands.
The core_script
or any other arguments passed for all the command types must be preserved in their original form and must be passed as is to tudo
without any variable expansion or history expansion, etc.
This can be done in two ways, either using single quotes to surround the core_script
and arguments or passing them with process substitution with a literal cat
heredoc
.
If you are using Termux:Tasker plugin to run tudo
commands, you would need to use single quotes to pass arguments, since it doesn't support process substitution. You would need to install Termux:Tasker version >= 0.5
since argument parsing is broken in older versions. Check the Passing Arguments Surrounded With Single Quotes section for more details. Check the Template 2
and Template 3
of the Termux Tasker Plugin Tudo Templates Task task for templates on how to use single quotes to pass arguments with Tasker. Basically, just set your script text to the %core_script
variable with the Variable Set
action and add any additional command options or arguments to the %arguments
variable.
If you are using a foreground terminal session or scripts to run tudo
commands, you can use single quotes to pass arguments or use process substitution. If you are using a foreground terminal session, then you must disable the bash
command completion and history expansion for the current terminal session before running tudo
command to pass multi-line arguments by running bind 'set disable-completion on'; set +H
. Check the Passing Arguments Using Process Substitution section for more details. Check the Examples section for templates on how to use process substitution to pass arguments.
If you are using RUN_COMMAND Intent to run tudo
commands with Tasker using the TermuxCommand()
function in Tasker Function
action, you don't need to surround the core_script
or arguments with single quotes, since arguments are split on a simple comma ,
instead. If your arguments themselves contain simple commas ,
(U+002C
, ,
, ,
, comma
), then you must replace them with the comma alternate character ‚
(#U+201A
, ‚
, ‚
, single low-9 quotation mark
) for each argument separately before passing them to the intent action and would also need to pass the -r
command option to tudo
. Check the Passing Arguments Using RUN_COMMAND Intent section for more details. Check the Template 2
of the Termux RUN_COMMAND Intent Tudo Templates Task task for a template on how to replace commas in each argument separately with Tasker.
If you are using RUN_COMMAND Intent to run tudo
commands with Tasker or other apps using the am
command, like using the Run Shell
action in Tasker, you need to surround all your arguments, like the core_script
and all other arguments with single quotes when passing them to the com.termux.RUN_COMMAND_ARGUMENTS
string array extra after you have escaped all the single quotes in the final value, since otherwise it may result in incorrect quoting if the arguments themselves contain single quotes. However, due to the string array extra, the arguments are still split on a simple comma ,
so if your arguments themselves contain simple commas ,
(U+002C
, ,
, ,
, comma
), then you would also have to replace them with the comma alternate character ‚
(#U+201A
, ‚
, ‚
, single low-9 quotation mark
) for each argument separately before passing them as the argument to the extra and would also need to pass the -r
command option to tudo
. Check the Passing Arguments Using RUN_COMMAND Intent section for more details. Check the Template 3
of the Termux RUN_COMMAND Intent Tudo Templates Task task for a template on how to replace commas in each argument separately and also escape single quotes in all the arguments with Tasker.
Note that for RUN_COMMAND Intent, any arguments passed to any command options or the main arguments to tudo
should also not be surrounded with single or double quotes to prevent whitespace splitting in the intent action, like done for usage with Termux:Tasker
plugin since splitting will occur on simple comma characters instead. Check the Template 4
of the Termux RUN_COMMAND Intent Tudo Templates Task task for a template for this.
Any argument surrounded with single quotes is considered a literal string and variable expansion is not done. However, if an argument itself contains single quotes, then they will need to be escaped properly. You can escape them by replacing all single quotes '
in an argument value with '\''
before passing the argument surrounded with single quotes. So an argument surrounded with single quotes that would have been passed like 'some arg with single quote ' in it'
will be passed as 'some arg with single quote '\'' in it'
. This is basically 3 parts 'some arg with single quote '
, \'
and ' in it'
but when processed, it will be considered as one single argument with the value some arg with single quote ' in it
that is passed to tudo
.
For Tasker
, you can use the Variable Search Replace
action on an %argument
variable to escape the single quotes. Set the Search
field to one single quote '
, and enable Replace Matches
toggle, and set Replace With
field to one single quote, followed by two backslashes, followed by two single quotes '\\''
. The double backslash is to escape the backslash character itself.
Escaping single quotes while running commands in a foreground terminal session will be much harder if there are many single quotes, same would apply for double quote surrounded strings, so use process substitution instead, check below.
The format is the following
tudo -s '
<core_script>
' '[some arg1]' '[some arg2]'
Process Substitution can be used to pass the core_script
and core_script_args
for the script
command type and to pass the command_args
for the path
command type when running tudo
from a foreground terminal session or from a script.
The following is the format for passing core_script
text.
tudo -s <(cat <<'TUDO_EOF'
<core_script>
TUDO_EOF
)
The following is the process substitution part
<(
)
Inside it there is a cat
Here Document. The script text should start after a newline after the 'TUDO_EOF'
part. You can type anything as script text other than TUDO_EOF
which when read, ends the script. The ending TUDO_EOF
should be alone on a separate line. The starting 'TUDO_EOF'
is surrounded with single quotes so that script is considered a literal string and variable expansion, etc doesn't happen.
cat <<'TUDO_EOF'
TUDO_EOF
Basically any text you type inside the cat
heredoc will be passed to the process substitution which will create a temporary file descriptor for it in /proc/self/fd/<n>
and pass the path to tudo
script so that it can read the argument text from it.
You can also read text from an existing script file using cat
and pass that to tudo
like the following
tudo -s <(cat "~/some-script")
To use RUN_COMMAND Intent that has arguments working properly, you need to install Termux version >= 0.100
and Tasker version >= 5.9.4.beta
. However, leading and trailing whitespaces from arguments will be removed for Tasker version < 5.11.1.beta
if you are using TermuxCommand()
function, so its advisable to use a higher version or use am
command instead.
If you are using the am
command, the format is am startservice --user 0 -n com.termux/com.termux.app.RunCommandService -a com.termux.RUN_COMMAND --es com.termux.RUN_COMMAND_PATH '<path>' --esa com.termux.RUN_COMMAND_ARGUMENTS '<one_or_more_args_seperated_with_commas>' --es com.termux.RUN_COMMAND_WORKDIR '/data/data/com.termux/files/home' --ez com.termux.RUN_COMMAND_BACKGROUND 'false'
If you are using the TermuxCommand()
function, the format is TermuxCommand(path,<one_or_more_args_seperated_with_commas>,workdir,background)
. The args can be of any count, each separated with a simple comma ,
. The only condition is that in the list the first must be path
and the last two must be workdir
and background
respectively.
For both the --esa com.termux.RUN_COMMAND_ARGUMENTS
string array extra and the TermuxCommand()
function, if you want to pass an argument that itself contains a simple comma ,
(U+002C
, ,
, ,
, comma
), it must be escaped with a backslash \,
so that the argument isn't split into multiple arguments. The only problem is that, the arguments received by the script being executed will contain \,
instead of ,
since the reversal isn't done as described in the am command source while converting to a string array. Tasker uses the same method. There is also no way for the am
command or the script to know whether \,
was done to prevent arguments splitting or \,
was a literal string naturally part of the argument.
// Split on commas unless they are preceeded by an escape.
// The escape character must be escaped for the string and
// again for the regex, thus four escape characters become one.
String[] strings = value.split("(?<!\\\\),");
intent.putExtra(key, strings);
tudo
uses an alternative method to handle such conditions. If an argument contains a simple comma ,
, then instead of escaping them with a backslash \,
, replace all simple commas with the comma alternate character ‚
(#U+201A
, ‚
, ‚
, single low-9 quotation mark
). This way argument splitting will not be done. You can pass the -r
option to tudo
which will then parse arguments as per RUN_COMMAND
intent rules to replace all the comma alternate characters back to simple commas. It would be unlikely for the core_script
or the arguments to naturally contain the comma alternate characters for this to be a problem. Even if they do, they might not be significant for any script logic. If they are, then you can set a different character that should be replaced, with the --comma-alternative
option. The -r
and --comma-alternative
options should ideally be the first options passed so that tudo
replaces the alternative comma characters from all arguments passed after the options.
For Tasker
use the Variable Search Replace
action on an %argument
variable to replace the simple comma characters. Set the Search
field to one simple comma ,
, and enable Replace Matches
toggle, and set Replace With
field to %comma_alternative
where the %comma_alternative
variable must contain the comma alternate character ‚
.
-
If you don't know what $PATH
, $LD_LIBRARY_PATH
and $PS1
variables or rc
files are or don't care to find out, then just run the commands below so that tudo
works properly, otherwise read the details below. Ignore No such file or directory
errors when running the commands.
sed -i'' -E 's/^(PS1=.*)$/\(\[ -z "\$PS1" \] \|\| \[\[ "\$PS1" == '\''\\s-\\v\\\$ '\'' \]\]\) \&\& \1/' "/data/data/com.termux/files/usr/etc/bash.bashrc"
sed -i'' -E 's/^(PS1=.*)$/\(\[ -z "\$PS1" \] \|\| \[\[ "\$PS1" == '\''%m%# '\'' \]\]\) \&\& \1/' "/data/data/com.termux/files/usr/etc/zshrc"
rc
files, short for run commands
, are shell specific files that are run or sourced whenever an interactive shell is started to define variables and functions etc.
Make sure in your rc
files like ~/.bashrc
file for bash
(where ~/
is the tudo shell
home), the $PATH
, $LD_LIBRARY_PATH
and $PS1
variables and any other variables exported by tudo
are not overridden, otherwise the tudo
commands will not work properly, since tudo
exports its own custom variable values which will get overridden when rc
files are sourced by any new shell started. You can run commands like tudo -v --dry-run --shell=bash su
to see what variables are normally exported for a given shell by tudo
.
Check the PATH and LD_LIBRARY_PATH Priorities section for more info on what these variables are.
For the $PATH
or $LD_LIBRARY_PATH
variables, either remove their variable set lines completely or if necessary only append any required paths to the existing variable values like export PATH="$PATH:/dir1:/dir2"
and export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/dir1:/dir2"
instead of overriding them with export PATH="/dir1:/dir2"
and export LD_LIBRARY_PATH="/dir1:/dir2"
in your rc
files.
The $PS1
variable, short for Prompt String 1, defines the characters you see at the start of the "line" when typing commands in shells running interactively like bash
or zsh
. For termux
bash
shell, this defaults to $
. For termux
zsh
shell, this defaults to %
.
If you want to allow tudo
to set its own default $PS1
value Ⲧ
or the one set with the $TUDO_SHELL_PS1
or $TUDO_POST_SHELL_PS1
variables in the tudo.config
file, then make sure the $PS1
value is not overridden by the shell rc
files, otherwise you will not be able to easily tell the difference between whether you are running a shell via tudo
or normally as the termux
user when you run commands like tudo su
. You can however check the value of $SHLVL
to see the nested shell level, run printenv | grep SHLVL
.
-
The
rc
files in$PREFIX/etc/
are sourced first whenever shells are started bytudo
. The$PS1
value is set and exported bytudo
before new shells are started, however, the value will get replaced if its overridden by therc
files when they are sourced during startup of the new shell.-
bash
shell currently uses the$PREFIX/etc/bash.bashrc
file, in which it sets the default value of$PS1
to\$
or\[\e[0;32m\]\w\[\e[0m\] \[\e[0;97m\]\$\[\e[0m\]
in recent versions. You need to replace the linePS1='\$ '
orPS1=<default>
with the conditional([[ -z "$PS1" ]] || [[ "$PS1" == '\s-\v\$ ' ]]) && PS1=<default>
so that$PS1
is only set if its not already set or is set to the default value internally used bybash
. You can run the commandsed -i'' -E 's/^(PS1=.*)$/\(\[ -z "\$PS1" \] \|\| \[\[ "\$PS1" == '\''\\s-\\v\\\$ '\'' \]\]\) \&\& \1/' "/data/data/com.termux/files/usr/etc/bash.bashrc"
to automatically do it or you can do it manually by runningnano "/data/data/com.termux/files/usr/etc/bash.bashrc"
. -
zsh
shell currently uses the$PREFIX/etc/zshrc
file, in which it sets the default value of$PS1
to%#
. You need to replace the linePS1='%# '
orPS1=<default>
with the conditional([[ -z "$PS1" ]] || [[ "$PS1" == '%m%# ' ]]) && PS1=<default>
so that$PS1
is only set if its not already set or is set to the default value internally used byzsh
. You can run the commandsed -i'' -E 's/^(PS1=.*)$/\(\[ -z "\$PS1" \] \|\| \[\[ "\$PS1" == '\''%m%# '\'' \]\]\) \&\& \1/' "/data/data/com.termux/files/usr/etc/zshrc"
to automatically do it or you can do it manually by runningnano "/data/data/com.termux/files/usr/etc/zshrc"
.
-
-
The
rc
files in~/
(defaulttudo shell
home) are also sourced afterwards whenever shells are started bytudo
. They must also not override the$PS1
value. However, if you want to set a custom value in them for usage outsidetudo
, then you can add conditionals to override$PS1
only if its not already set or is set to the defaulttermux
value set by$PREFIX/etc/*
rc
files.-
bash
shell defaultrc
file set bytudo
is~/.bashrc
. You can for example set$PS1
to£
by adding the line([[ -z "$PS1" ]] || [[ "$PS1" == '\$ ' ]]) && PS1='£ '
to it, where'\$ '
is the default value forPS1
in$PREFIX/etc/bash.bashrc
file. -
zsh
shell defaultrc
file set bytudo
is~/.zshrc
. You can for example set$PS1
to£
by adding the line([[ -z "$PS1" ]] || [[ "$PS1" == '%# ' ]]) && PS1='£ '
to it, where'%# '
is the default value forPS1
in$PREFIX/etc/zshrc
file.
-
This will ensure that the exported $PS1
variables will not be overridden by rc
files for bash
and zsh
. For other shells that may use the $PS1
variable, you can use similar conditionals in their rc
files.
There are limits on the arguments size you can pass to commands or the full command string length that can be run, which is likely equal to 131072
bytes or 128KB
for an android device defined by ARG_MAX
but after subtracting shell environment size, etc, it will roughly be around 120-125KB
but limits may vary for different android versions and kernels. You can check the limits for a given termux session by running true | xargs --show-limits
. If you exceed the limit, you will get exceptions like Argument list too long
. You can manually cross the limit by running something like $PREFIX/bin/echo "$(head -c 131072 < /dev/zero | tr '\0' 'a')" | tr -d 'a'
, use full path of echo
, otherwise the echo
shell built-in will be called to which the limit does not apply since exec
is not done.
Moreover, exchanging data between Tasker
and Termux:Tasker
is done using Intents, like sending the command and receiving result of commands in %stdout
and %stderr
. However, android has limits on the size of actual data that can be sent through intents, it is roughly 500KB
on android 7
but may be different for different android versions.
Basically, make sure any data/arguments you pass to tudo
script directly on the shell or through scripts or using the Termux:Tasker
plugin or RUN_COMMAND Intent intent is less than 120KB
(or whatever you found) and any expected result sent back if using the Termux:Tasker
plugin is less than 500KB
, but best keep it as low as possible for greater portability. If you want to exchange an even larger data between tasker and termux, use physical files instead.
The argument data limits also apply for the RUN_COMMAND Intent intent.
The word executable will be used henceforth for binaries, scripts and any other executable files.
Termux
executables currently exist at /data/data/com.termux/files/usr/bin
and /data/data/com.termux/files/usr/bin/applets
Termux
libraries exist at /data/data/com.termux/files/usr/lib
.
Android
executables normally exist at /system/bin
and/or /system/xbin
Android
libraries exist at /system/lib
and/or /system/lib64
.
When tudo su
commands is run, then the termux executables paths are prepended to android executables paths in the $PATH
variable. The termux library paths are prepended to android library paths in the $LD_LIBRARY_PATH
variable. This gives priority to termux paths.
When tudo asu
commands is run, then the android executables paths are prepended to termux executables paths in the $PATH
variable. The android library paths are prepended to termux library paths in the $LD_LIBRARY_PATH
variable. This gives priority to android paths.
The $PATH
variable sets the paths to search for executables when commands are executed. The $LD_LIBRARY_PATH
variable sets the paths to search for libraries for dynamic linking required by the commands that are executed. The path that appears first in both the variables is searched first and if the required binary, executable or library is found, that is the one thats used without looking further.
There are a few important things to consider when using tudo
with termux.
A executable that you want to run may exist in both termux and android executable paths but you may want to run a specific one. If you want to run the termux one instead of the the android one then run tudo su
command and then run the command to run the executable. If you want to run the android one instead of the the termux one then run tudo asu
command and then run the command to run the executable. However in both cases, if you write the absolute path of the executable instead of just writing its basename, the executable at the path you wrote will be executed even if the other ones path exist before in the $PATH
variable.
Another thing to consider is that dynamic library linking errors may occur when executables try to link to the wrong library. Executables should be linked with libraries they are compatible with and that define all the needed functions needed by the executable. Executables that exist in termux executable path should ideally be linked with libraries that exist in termux library path. Executables that exist in android executable path should ideally be linked with libraries that exist in android library path.
When an executable is run, the paths in the $LD_LIBRARY_PATH
variable are searched for the library that is required and whichever matching library is found first is used, even if that library is not compatible with the executable. If the library is indeed incompatible a linking error occurs with errors that may include words like CANNOT LINK EXECUTABLE
and cannot locate symbol some_symbol referenced by /lib....
.
So if an executable in android executable path tries to link with a library in termux library paths to which it is incompatible with, then a linking error will occur. This is likely to happen with some executables including the android dumpsys
or input
binaries among others. A linking error may occur the other way around too, when a termux executable tries to link with libraries in android library path. To prevent these linking error from occurring in most situations, separate tudo su
and tudo asu
commands exist, which set the correct order of paths in the $PATH
and $LD_LIBRARY_PATH
variables so that normally termux executables are linked with termux libraries and android executables are linked with android libraries whenever either command is run.
However, another way to automatically prioritize android libraries is by running the path
command type with tudo <command>
. If the command
exists in the /system
partition, then android library paths are prepended to termux library paths in the $LD_LIBRARY_PATH
variable automatically. An absolute path is not needed to be passed for this to work as the $PATH_TO_EXPORT
is automatically searched. This is helpful for situations when you are already in a tudo su
shell and do not want to shift to the tudo asu
shell or unset $LD_LIBRARY_PATH
to run just one executable in android executables paths.
You can also use the tpath
and apath
functions if they are defined in the rc
file of your interactive shell to shift priorities.
Normally tudo su
will work fine without problem when dropping to tudo
shell. But if you want to specifically run an executable in the android executable paths instead of the one in termux executable paths or are getting linking errors when running android executables with tudo su
, then try using tudo asu
and then running the required command or use tudo <command>
or tudo -a <command>
.
For the shells bash zsh dash sh fish ksh
, additional functions named tpath
and apath
are added to their rc
files if the tudo
script creates the rc
files, they are not added otherwise. You can call these functions to set priorities from inside interactive shell sessions only when running tudo su
, tudo asu
or tudo -is <core_script
commands, since they depend on some environmental variables set by the tudo
script and are not hard-coded in case of future changes.
The tpath
function will set priority to termux bin and library paths in $PATH
and $LD_LIBRARY_PATH
variables.
The apath
function will set priority to android bin and library paths in $PATH
and $LD_LIBRARY_PATH
variables.
The functions allows the users to quickly switch priorities without having to switch between tudo su
and tudo asu
shells.
If you already have an existing rc
file for your shell like ~/.bashrc
and want to add the functions to it. Just temporarily move (not copy) the file to somewhere else and run tudo su
command with the optional --shell
option, then copy the functions from the new rc
file created by tudo
to your old file, then remove the new file and move the old file back.
For the fish
shell, additional functions named export
and unset
are also added to the rc
files if the tudo
script creates its rc
file, they are not added otherwise. The functions port the bash
export var=value
and unset var
functionality respectively.
Check the tudo_tests script to run automated tests for the tudo
script command types, options and shells. Usage instructions are inside the script. There are more examples for running tudo
inside the tudo_tests
script that can be used by users, although may not be too user friendly to view or understand.
Check FAQs_And_FUQs.md file for the Frequently Asked Questions(FAQs) and Frequently Unasked Questions(FUQs).
Check CHANGELOG.md file for the Changelog.
-
-
- To donate money to support me, you can visit here for more info.