does not display or operate correctly. The cause of the problem is the <<< because removing it fixes the problem. (I can provide further details about the macro and how it misbehaves if ‘<<<’ is present, but I don’t see how it would help since the cause of the problem is known.) Using triple double quotes instead of the triple single quotes does not fix the problem. Using the macrocall widget instead results in the exact same problem occurring.
Is there any way to include a triple less-than string (<<<) in a macro call?
Using tripled single-quotes surrounding the macro parameter value is not supported syntax for macro calls.
You CAN use tripled double-quotes around the macro parameter value; however, because the value in your example ends with a double-quote, you need to include an extra trailing space to separate it from the tripled double-quotes, like this:
Alternatively, to avoid the extra trailing quote in the clipboard contents, you can use doubled square brackets to enclose the macro parameter value, like this:
Thanks, Eric. I was sure in my experimenting that I’d started with tripled double quotes (with trailing space) and they had not worked, but on testing again I see it does work.
The use of doubled square brackets to avoid the trailing space appeals to my sense of neatness. I did find that you cannot include single square brackets inside a macro parameter value if you use doubled square brackets. For example, this:
Without giving a specific answer we often move “more difficult to handle strings”, those containing part of the tiddlyWiki script language, to macros/procedures and maybe functions.
Rather than use the short form to call <<macros p1>> /procedures consider using the long form $macrocall or $transclude $variable.
copy-to-clipboard-above-right is in the doc macros or is it a custom macro?, perhaps you can redesign/create the macro so the parameters need not have such parameters passed.
The New substitute operator may be another approach