I don't think that this is possible due to how the parser works. Because there is the macro call widget that can be used to get around the problem I don't think anyone is very motivated to dig into the parser and try and fix it because fixes like that often come with enough edge case problems to cause nightmares.
And I think that it is the >> part that is specifically breaking it, this may be able to be used to get around the problem in some cases. I don't see how to use it in this one, but in the past I have been able to cheat and put the first > in one macro and the second > in another one and build a string that contained things that couldn't go into a single argument. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/467df3f6-3234-456d-83e9-63abccb21e66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
