My bad, that was a typo caused by my text editor’s bracket autocomplete. It does work with the typo fixed, which is strange because I swear this has not worked for me before. Maybe at the time I didn’t know anything about TiddlyWiki and I was doing something else wrong. Learned something new, thanks!
Tones, I would think the benefit is that the <__parameter__> syntax can’t get messed up by quoting, no matter what is in the parameter (same reason you might want to use it outside a filter). In your version, if there was a double-quote in the name of the tag, the filter would break. You could use triple quotes around the filter, but then triple quotes would mess it up, and so on. On Wednesday, November 25, 2020 at 6:19:55 PM UTC-6 Mark S. wrote: > The angle braces REPLACE the square brackets in filter expressions. So > your code should look like: > > \define testme(parameter) > <$list filter="[tag<__parameter__>]"> > <$link to=<<currentTiddler>>/><br> > </$list> > \end > > > > On Wednesday, November 25, 2020 at 11:48:56 AM UTC-8 soren.b...@gmail.com > wrote: > >> On Wednesday, November 25, 2020 at 1:09:22 PM UTC-6 Mark S. wrote: >> >>> Inside a filter, a variable could be referenced as tag[$art$] or as >>> tag<__art__> . >>> >> >> Really? Did that work for you? I thought parameters-as-variables only >> work in a strict transclusion context with double angle brackets. In a >> simple test it yields a syntax error: >> >> \define testme(parameter) >> <$list filter="[tag<__parameter__>]]"> >> <$link to=<<currentTiddler>>/><br> >> </$list> >> \end >> >> <<testme Section>> >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f1430e06-a24f-4703-8b27-18f88c1a5908n%40googlegroups.com.
