An even better example would be something like:
*\define concat(1 2 3 4 5) $1$$2$$3$$4$$5$*
*<<concat abc{{ Getting Started } }def>>*
making it clearer that there's nothing special about *{{* and *}}* being
first and last in the macro's result string.
A counterexample would also be good:
*\define itself(x) $x$*
*<<itself {{GettingStarted>>}}*
That one *doesn't* transclude anything, because the return value of the
macro call is parsed in isolation, so it can't see the closing *}}* and so
doesn't match the syntax for a transclusion.
Pushing the edge cases still further:
*{{<<itself GettingStarted>>}}*
results in nothing at all. The macro call returns the string
*GettingStarted*, which the parser then recognises as a link – and this
link then makes no sense within the transclusion brackets.
– æ
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
