Hi NT,
Eric's examples work fine for me.
Remember, macros need to be declared *at the beginning of a tiddler*.
There are two ways to declare macros...
1) one-liner
\define mymacro() do stuff
2) multiline macro
\define mymacro()
do stuff
\end
Only the latter requires you to close it via *\end*.
You can combine the two freely...
\define a() a
\define b()
b
\end
\define c() c
\define d()
d
\end
<<a>><<b>><<c>><<d>>
The above even works whith empty lines at the beginning or accidental
blanks after *\end*.
You can, in fact, leave any arbitrary white space (newlines, blanks, tabs,
etc...) between the macros and TiddlyWiki will understand you,
so long as the macro declarations are at the beginning of the tiddler.
> The link used in a macro seems to break something. Is that normal? Is that
> a bug?
> Is it naturally necessary to mask the link somehow to avoid this problem?
>
To debug your macros:
- output test content, e.g.
- *<<currentTiddler>>*
- *<<myVar>>*
- *<$text text="$some-param$">*
- remove any code that appears to be broken to find the spot that breaks
it
- it is easy to forget closing a* <<macro*
- likewise it is easy to not close a *<$widget>* like this ....should
always close the *</$widget>*
Best wishes,
- tb
--
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 http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/99ee1a43-6c71-45e5-b85e-017e7a6f722b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
