Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Btw u/joaomgcd I couldn't even add my email between angle brackets like author: agnostic-apollo to the Control section of the help anchor (1st action of task) without tasker considering it as html and collapsing everything to a single line in actions list rendering of the anchor. That format is the RFC822 standard, I had to use author: agnostic-apollo ([email protected]) instead for now, but I shouldn't have to go against standards just to appease tasker. Consider adding support for as the first line of Anchor action and action labels to disable html or any other rendering as we discussed a while back. No need for markdown support now, just allow a way to disable that annoying rendering and also don't show the DOCTYPE line when rendering. Thanks.
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.