> > Consider the below example in which a macro output contains some wikitext > has been fed to a wikify widget! > > > \define mc() This is a `code` and __underline__. > > > > <$wikify name="result" text="""<<mc>>"""> > > <<result>> > > </$wikify> > > Result is: > > This is a code and underline. > > While I expect an output like this: > > This is a code and *underline*. > > > What is the problem? Note to the code and underlined text! > > --Mohammae > > Note: The use case is to store the result and send it to another widget > (another scope) > > > Hi Mohammad, in cases like this, the wikiparser does its magic first ...
do you remember the example I gave you, where I wikified the text field of another tiddler, but viewing it with <$view tiddler="bla" mode="block" format="text"/> <$wikify name="something" text="""<$view tiddler="bla" mode="block" format="text"/>"""> <<something>> </$wikify> the view widget here assures that the plain text comes in ... in your example here you have no such "helper" ... if you change your mc macro to \define mc() \rules only This is a `code` and __underline__. \end ... you prevent the parser from kicking in in this macro block and it works -- 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/0239dc6f-0924-47c5-a75f-0baf82f5e088%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
