On Monday, May 4, 2020 at 12:07:32 AM UTC+2, TonyM wrote:
...
Having every macro in 1 tiddler can improve the possibility to document
> them. The text below a macro definitions is ignored by the \import process.
> So it doesn't have any memory or performance penalty if there is a lot of
> text there.
>
>> But .. I personally think, it makes debugging more complex.
>
>
> Good to know, So If I placed in the body macro documentation is will be
> visible on the macro tiddler but not add too much to slow down?
>
> For example?
> \define first-tiddler(filter:"[tag<currentTiddler>]") {{{ $filter$ +[first
> []] }}}
> \define last-tiddler(filter:"[tag<currentTiddler>]") {{{ $filter$ +[last
> []] }}}
> \define next-tiddler(filter:"[tag<currentTiddler>]") {{{ $filter$ +[after
> []] }}}
> \define prev-tiddler(filter:"[tag<currentTiddler>]") {{{ $filter$ +[before
> []] }}}
>
> <h2>Macro definition tiddler</h2>
>
> ;Obtain the first/last/next/prev member in a list defined by filter
> :Defaults to tiddlers tagged with the current tiddler,
> `[tag<currentTiddler>]`
> *`<<first-tiddler [filter]>>`
> *`<<last-tiddler [filter]>>`
> *`<<next-tiddler [filter]>>`
> *`<<prev-tiddler [filter]>>`
>
> <!-- comment here ok? search keywords etc... -->
>
<h2> ... is already comment. So you can see it, if open the tiddler in view
mode.
If you the following line to a tiddler tagged: $:/tags/Macro you'll see the
code in view mode.
<pre><$view field="text"/></pre>
So your comment could be text only. .. no need to use <!-- comment -->
All kudos for the <pre> ... line above go to Eric Shulman.
The <pre>... definition isn't possible, if you use a tiddler as a template,
or if you want to transclude it.
have fun!
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/f7adaef1-640b-4dfe-99b5-2e801840406d%40googlegroups.com.
