Today I wanted to see which tiddlers I have that are javascript. In advanced research i can execute something like
[get[type]match[application/javascript]] but it would only bring "application/javascript" I can't have [filter[get[type]match[application/javascript]]] because this is gross syntax error. But if I had access to another input ext for a macro to be called extra I could do extra : [get[type]match[application/javascript]] research : filter<extra>sortan[] and the job would be done. BTW, I think a standard "nop" macro doing nothing would be useful. I'm using it many times when I have to decide for an eventual treatment, for (actual real) instance: \define deleteProjectNewAltjson(target id) <$action-log $$message="delete project «$target$##$id$»"/> <$action-deletefield $tiddler="$target$" $field="$id$"/> <$set name=next-step filter="[<target>getindex<id>]then[_kludge4deleteProjectNewAltjson]else[nop]]"> <<next-step "$target$" "$id$">> </$set> <$action-log $$message="deleted project «$target$##$id$»"/> \end (this concerns a potential bug for impossibility to delete a property of first level within a json object tiddler -- there is a separate thread I fielded yesterday for that) I have not seen any other way to have a conditional call to a macro. regards, -- Jean-Pierre -- 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/a5a970de-75ce-427d-b655-62c8e27301e4n%40googlegroups.com.
