Use it as below. <$macrocall $name=foo x=<<text>> />
But this is not nested macro! By nesting it means a macro inside another macro as internal macro. Seems this not possible in Tiddlywiki. Not directly related but useful https://kookma.github.io/TW-Scripts/#Nestetd%20Macro%20-%20Passing%20Variable --Mohammad On Saturday, January 19, 2019 at 11:29:55 PM UTC+3:30, Joe Armstrong wrote: > > > I have two macros > > \define text() > A line of text > \end > > \define foo(x) > fooStart $x$ fooStop > \end > > So > > <<text>> is replaced by "A line of text" > > and > > <<foo "abc">> is replaced by "Start abc fooStop" > > But <<foo <<text>> >> > > is replaced by "fooStart <<text fooStop >>" > > And NOT "fooStart A line of text fooStop" as I had expected. > > After a lot of head scratching I realised that this means that the > argument (x) to foo is the > string "<<text" ie the first occurrence of ">>" to the left > of the start "<<" of the macro and not the second occurrence. > > ie. "<<" and ">>" do not properly nest as I had expected. > > This seems like a pretty big pothole for a beginner to fall into ... > > So what is the accepted idiom for using a macro result > as the input argument to another macro - how does one chain macro calls > together? > > Cheers > > /Joe > > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/39eaab46-71eb-4b4b-9a7b-25b0713a64e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
