Hi Mat,
 

> Now, I can't fully follow the syntax - e.g how does the placeholder 
> %inputTitle% know the the term inputTitle? Is this a hardcoded keyword?
>

Yes, and it's a variable that is set to each input title in turn when the 
subfilter is evaluated against it ...unless you'd declare a custom variable 
in the suffix like so:

a b c +[filter: var:foo<some-subfilter>]

..then this variable *foo* will be set instead ...first to *a*, then to *b* 
and finally to *c*. 

...but, more importantly for the OP, I'm wondering this also search the 
> field name itself, or only the field value?
>

There is no filter yet that matches some substring of a field, yet.

I think the *has* filter operator <http://tiddlywiki.com/#has%20Operator> can 
and should be amended to cater for basic wildcards, e.g.:

   - has:prefix-*[]
   - has:*-suffix[] 

Does "found for the fields" mean "found in the field values for..." or 
> perhaps both "found in the field titles and/or the field values for..."
>

It means "in the field value" ...not the field names.
The field-names simply specify in which fields to search
not which field-names to search for.
 

> As you know, normal search does search both the tiddler titles and the 
> text fields - and even top-ranks title hits - so it would be very good if 
> this was also the case with your method!
>

You can always construct cascaded filters where one field gets added first 
and some other(s) later.
 
Best wishes,

Tobias.

-- 
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/78db2c2c-67d1-4d34-aea5-e6d1f324398f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to