<$list variable="filter_field" filter="[enlist<flfields>]"> <$wikify name="search_string" text="[<<filter_field>>[<<currentTiddler>>]!prefix[View]!prefix[Template]first[]]"> <$wikify name="display_string" text="[<<filter_field>>[<<currentTiddler>>]!prefix[View]!prefix[Template]]"> <$list variable="search_confirm" filter=<<search_string>> > <$set name="display_tag" filter="[<search_confirm>tags[]] -stub"> <fieldset class="custom_fieldset"> <legend> <span class="section_label"> @@text-transform: capitalize;<<display_tag>>@@ </span> </legend> <$list filter=<<display_string>> >
</$list> </fieldset> </$set> </$list> </$wikify> </$wikify> </$list> This is the code I have (and it is working now, thanks to the suggestion I saw earlier), but it's nasty. The problem with the macro solution you mentioned is I needed a more general, flexible solution to use as a list filter. In the code above, the field I'm checking is stored in a variable. "[<var1>[<currentTiddler>]]" doesn't work, so I had to wikify it to make it work. I was hoping for something with a syntax similar to <currentTiddler>listed<var1>, since it's a simpler piece of code than the mess of wikifying I have above. On Sunday, December 22, 2019 at 2:22:21 PM UTC-6, Eric Shulman wrote: > > What I want is some way to find all tiddlers that contain a field where >> the field's entire value matches "Constitution Class" (or whatever other >> string I throw at it), rather than enlisting every fields' contents to find >> the value. >> > > Based on the above statement... and using the example values you > indicated, this should do what you want: > <$list filter="[craft_class[Constitution Class]]"> > <<currentTiddler>><br> > </$list> > > More generically, you could write a macro like this: > \define getAllMatches(fieldname,fieldvalue) > <$list filter="[$fieldname$[$fieldvalue$]]"> > <<currentTiddler>><br> > </$list> > \end > > which you would invoke as: > <<getAllMatches "craft_class" "Constitution Class">> > > >> *I do not want any more plugins. Please do not suggest one.* >> > > This little message seems quite harsh... especially repeated twice, > and in bold text, on every message you post. > > If you don't want plugins, you could just say: > "I'm looking for a native TW5 way to solve this without using a plugin" > > The people in this group are a helpful bunch and are generally willing > to put in quite a bit of effort to solve other people's problems. > > Rather than telling them what kind of solutions you will accept, > just ask for help finding ANY solution to your problem. > > Then, if someone offers a solution that involves a plugin, > and you don't want plugins, just politely ignore that solution. > > -e > Eric Shulman > TiddlyTools.com: "Small Tools for Big Ideas! (tm) - > http://www.TiddlyTools.com (TWClassic) > InsideTiddlywiki - http://www.TiddlyTools.com/InsideTW (TW5) > -- 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/a937cd6e-7632-4192-813e-acc00db6681a%40googlegroups.com.
