Hi Eric Your example of
\define x(y:<<currentTiddler>>) is actually equivalent to: \define x(y:"<<currentTiddler>>") The technique you are using is to pass the attribute brackets as part of the parameter string. If the parameter isn't specified then it is given the literal string value "<<currentTiddler>>", and not the actual value of the variable "currentTiddler". So it only works if the parameter is eventually wikified, so that the macrocall syntax is processed. Another problem is that macro calls currently cannot be nested, so you cannot do: <<x y:"<<myVariable>>">> There's also a trap that this won't work: <<x y:"My Tiddler">> Instead you have to do: <<x y:"[[My Tiddler]]">> Best wishes Jeremy On Tue, May 5, 2015 at 7:40 PM, Eric Shulman <[email protected]> wrote: > On Tuesday, May 5, 2015 at 11:00:02 AM UTC-7, Jeremy Ruston wrote: >> >> The default values for macro parameters can only be specified as literal >> strings, I'm afraid. Can you expand on the situation, perhaps I can advise >> on alternatives? >> > > I just tried this on TiddlyWiki.com: > \define x(y:<<currentTiddler>>) > $y$ > \end > <<x>> > .. and it WORKS! > > and just to be sure it wasn't some magic involving <<curerntTiddler>>, I > also tried > > \define z() > This is some text > \end > \define x(y:<<z>>) > $y$ > \end > <<x>> > and it works also. > > @Jeremy: It is possible your implementation is just so good that it > handles a case you didn't expect? > > -e > > > > -- Jeremy Ruston mailto:[email protected] -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJYc1hRg_0ax_SWRendAbN3CApDBTcLnL%2BwihtH%3D8WNX1g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
