Tasker-XML-Info VS tasker_config_utils

For tasker xml structure, check https://github.com/Taskomater/Tasker-XML-Info

As for users on old versions of Android, I am one of those, still on Android 7. Official reddit app min version is Android 6. Tasker's min version is Android 5, so not really an issue. And 12 of Tasker's actions have been deprecated. Users should use the official app if the 3rd party apps aren't updated to latest reddit specs. Cause if fenced code block from years ago is still not supported, its most likely those apps have lot of other stuff broken as well. If you wanna use them, by all means use it, but don't complain for broken stuff to official reddit app users, but to the respective 3rd party app devs.

XML editing is the way to go if you can understand how tasker XML works. Check Tasker XML Info for some details. I do it quite often to modify hundreds of actions/tasks which would otherwise take days and weeks to manually edit, possibly with lots of typos/mistakes. When adding literal values, make sure to convert ascii characters to XML special characters like & to '&', < to '<' and > to '>' like tasker_config_utils does in reverse when reading, otherwise XML would break.

https://github.com/Taskomater/Tasker-XML-Info#tasker-xml-file-nodes-and-tags

And would be more useful to get the project/profile/task name as well. You can do a Data Backup and get the nme and name tag value for the id defined in the variables xml file for each variable. Probably should be easy with Structured Output. Tasker backup design info can be found at Tasker XML Info.

Unrelated, for understanding tasker xml, Tasker-XML-Info might be helpful.

I'm referring to this utils

You can also pass description to the generate_info command of tasker_config_utils to get detailed info of task with the description included.

You can use tasker_config_utils task description option of generate_info command for that.

XML editing is the way to go if you can understand how tasker XML works. Check Tasker XML Info for some details. I do it quite often to modify hundreds of actions/tasks which would otherwise take days and weeks to manually edit, possibly with lots of typos/mistakes. When adding literal values, make sure to convert ascii characters to XML special characters like & to '&', < to '<' and > to '>' like tasker_config_utils does in reverse when reading, otherwise XML would break.

https://github.com/Taskomater/tasker_config_utils#examples

Also after going through tasker_config_utils that's pretty amazing!

It's not the printing that's the issue, it's actually reading the xml. I'm using sed command to read the xml nodes with regexes, line by line, so indentation of each node and sub node is very important to know when each node ends safely. There are utilities available for xml parsing but they might not work as easily for the craziness I'm doing. Also sed makes it very easy to get or match tags above and below something with regexes, something like that would likely not be that easy to implement with xml parsers easily if at all. Running random regexes to get random stuff is pretty easy this way.

No Thanks! I already have enough horror stories to last a lifetime :p