I am looking at some older example tbx files that I found on my drive. There is a note readme:
“This is a simple demo to show a way to replace straight single/double quotes with their ‘smart’ equivalents.
In applying these techniques in a real world situation, it is worth noting that constantly running a lot of command line code all the time is probably not ideal for the agent update cycle. Think about approaches like having the code in an agent that can be run at low priority or only turned on and run when needed.”
There are three other notes. The first is “quotify” and its $text is set to a SED statement that does clever things with quotes. The next is TestText that holds a short text containing dumb quotes and a rule:
$MyString = runCommand($Text(quotify),$Text);
The last note is named “out” and displays the output.
Looking at the rule I believe that the text of quotify is being run with $Text as a command and the results are being stored in attribute $MyString. But this is not what happens, the attribute $MyString remains blank while the note “out” is populated with the result. I wonder how this happens?quotify.tbx (55.4 KB)