Tasker variables in the arguments field?

[termux]

Tasker variables in the arguments field?

[jschwinger233]

for the variables generated by profile, like App Changed: Package(%app_package), you have to set another variable to the value in task to make tasker:termux parse properly, like %var=%app_package, then just fill the arguments with %var

[Sokonomi]

Append; I just saw there was a fork that got merged that supposedly added the use of tasker variables. Please work on putting up some documentation up about this plugin; Apparently it does stuff that only the devs themselves know about.

[MolotovCherry]

I've been putting Tasker variables into the arguments field, seems to work fine for me

[leo60228]

@Sokonomi It seems that you can just prefix arguments with % and they get treated as Tasker variables. Works with Automate, which I prefer to Tasker.

[dekiesel]

for the variables generated by profile, like App Changed: Package(%app_package), you have to set another variable to the value in task to make tasker:termux parse properly, like %var=%app_package, then just fill the arguments with %var

Thanks, that was it! It seems you need to turn global variables (variables containing one or more uppercase characters) into local variables (variables ONLY containing lower case characters). I just tried this with a "Variable Set" and it works as expected.

[agnostic-apollo]

Only local variables (all lowercase letters) can be passed to plugins in Tasker and not global. Check TaskerPlugin Library addVariableBundle() function.