[tw5] Re: Just a Filtering Code Pattern

I think that deleted reply was mine. I will copy and paste from Tiddlytalk --- @Télumire . It’s true. They works like an OR. {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] }}} also return different result. This behaviour would be documented. El martes, 28 de septiembre de 2021 a las 2:41:03 UTC+2,

[tw5] Re: Just a Filtering Code Pattern

@Télumire . It's true. They works like an OR. `{{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] }}}` also return different result. This behaviour would be documented. El lunes, 27 de septiembre de 2021 a las 14:08:07 UTC+2, jn.pierr...@gmail.com escribió: > Just a thought: it would be fine if the

[tw5] Re: Just a Filtering Code Pattern

JP, One way of handling all tags on the current tiddler is not to use the various tag operators but address the tags field directly. [all[current]get[tags]] returns the content of the tags field which includes all tags. Does this meet with your requirement? On Monday, 27 September 2021 at

[tw5] Re: Just a Filtering Code Pattern

You would need something to wrap tags that have spaces in them. The "what" to wrap that in, no idea. On Monday, September 27, 2021 at 9:08:07 AM UTC-3 jn.pierr...@gmail.com wrote: > Just a thought: it would be fine if the tagging operator could have a > "all" parameter which would select

[tw5] Re: Just a Filtering Code Pattern

Just a thought: it would be fine if the tagging operator could have a "all" parameter which would select tiddlers tagging all of the tags in input (currently, that's "any tag is enough"). Thus we would have a simple and readable solution as: {{{ [tag1 tag2 tag3 tag4 +[tagging:all[]]] }}} Le

[tw5] Re: Just a Filtering Code Pattern

Hello all ! The filter syntax provided by @Álvaro is very neat but doesnt match the requirements of cj.v : counting the tiddlers with 4 specifics tags and only those tiddlers. See this screenshot : https://i.imgur.com/lVlsYZt.png I think it's because the commas imply an OR condition, but

[tw5] Re: Just a Filtering Code Pattern

- In the fields cases we have a workaround with `fields` operator. It has suffixs (exclude, include) - I think that there in't any tiddler with those tags. The search is the tiddler with all these tags (¿and any other?) In the case of titles, you find a issue, but I don't know its reason. I

[tw5] Re: Just a Filtering Code Pattern

Of even this {{{ [tag[Common Operators],[HelloThere],[TableOfContents]] }}} On Sunday, 26 September 2021 at 00:27:45 UTC+10 TW Tones wrote: > Very interesting. > > I think he documentation should be expanded to detail this. Multiple > parameters to operators are only documented in a few

[tw5] Re: Just a Filtering Code Pattern

Very interesting. I think he documentation should be expanded to detail this. Multiple parameters to operators are only documented in a few operators, but if I read this correctly they can work on operators in *general*? If general you may expect this to work ```{{{

[tw5] Re: Just a Filtering Code Pattern

I just tested this on both 5.1.23 and 5.2.0pre. I created one tiddler containing ``` {{{ [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] :filter[tags[]count[]compare:eq[4]] }}} ``` and another tiddler with the four tags (note capitalization and spaces in the tag values). It *does* seem to work on both

[tw5] Re: Just a Filtering Code Pattern

Alvaro; You suggested something like this {{{ [tag[Tag 1]**,**[Tag 2],[Tag 3],[Tag 4]] :filter[tags[]count[]compare:eq[4]] }}} As far as I can see this does not work on the pre-release and the t6ag format [tag[Tag 1],[Tag 2],[Tag 3],[Tag 4]] (simplified) is not documented Does not work. So

[tw5] Re: Just a Filtering Code Pattern

I don't know if I understand you. El sábado, 25 de septiembre de 2021 a las 5:31:18 UTC+2, TW Tones escribió: > Alvaro; > > Have you tested this? > > {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]] > :filter[tags[]count[]compare:eq[4]] }}} > > I cant see it working. Here

[tw5] Re: Just a Filtering Code Pattern

Alvaro; Have you tested this? {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]] :filter[tags[]count[]compare:eq[4]] }}} I cant see it working. Here is says * NEW IN: 5.1.23 Filter operators support multiple parameters which are separated by a ,

[tw5] Re: Just a Filtering Code Pattern

For an easy reading, edit your tiddlers with a fixed font like courier or terminal. Le vendredi 24 septembre 2021 à 19:15:47 UTC+2, Álvaro a écrit : > I don't know if they are loving that or not. The commas aren't easy to see > between brackets (for me). If I begin on end of filter run, i also

[tw5] Re: Just a Filtering Code Pattern

I don't know if they are loving that or not. The commas aren't easy to see between brackets (for me). If I begin on end of filter run, i also have this problem. But any can build his/her mental shorcuts to avoid it. If someone can't solve a problem, maybe he/she can create a "alternative way"

[tw5] Re: Just a Filtering Code Pattern

I was thinking that the tagging operator was the zay to get tiddlers that all share all of the tags in input. That's what the dec say: "output: the titles of any tiddlers that carry the input tags". So my function would be: \define fun(tags) <$vars four="[tags[]count[]match[4]]"> <$set

[tw5] Re: Just a Filtering Code Pattern

I just discovered the other thing that causes me problems: lack of proximity. I do find it difficult looking at "Tag 4" in that filter and not seeing the filter operator right before it. So I see the comma, and I backtrack away from "Tag 4" to figure out the filter operator is "tag". That

[tw5] Re: Just a Filtering Code Pattern

Oh man, that is pretty awesome. I can see the majority of the folk loving that. But you're right, for my disability, that isn't explicit enough for me to distinguish what's going on. Too many ways of specifying individual tags, and I start getting into some cognitive overload. I'm the same

[tw5] Re: Just a Filtering Code Pattern

It works fine. I tried to find a alternative, but I wasn't lucky. When I resee your filter, I remember about the multiple parameters in filter operator with commas (from last version, 5.1.23). And we can add a second filter run that it applies your filter to result of first run. Then you can

[tw5] Re: Just a Filtering Code Pattern

That's fine by me. And yes filters are fun even if sometimes a bit tricky. So for the fun of it, you could arrange your filter so that the input would be the 4 tags you want. something like that: \define fun(tags) <$set variable=occ filter="[[$tags]put your filter code