[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, TW Tones escribió:
> 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 22:08:07 UTC+10 jn.pierr...@gmail.com
> wrote:
>
>> 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 lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>>
>>> 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 here we want
>>> an AND :)
>>>
>>> So with a a tiny bit of tweaking the correct filter is :
>>>
>>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> Here's a live demo :
>>>
>>>
>>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>>
- 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
was trying to find a workaround but i wasn't lucky. I also found that the
match operator doesn't support multiple parameters.
El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
escribió:
> 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 operators, but if I
>> read this correctly they can work on operators in *general*?
>>
>> If general you may expect this to work ```{{{
>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>
>>> 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 versions of TW
>>> -e
>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>
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 I asked if you tested this?
On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
> 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
>> is says
>>
>> * NEW IN: 5.1.23 Filter operators support multiple parameters
>> which are separated by a , character.*
>>
>> *For example: [param1],[param2] or ,{param2}*
>> However as far as I can see only if such multiple parameters are
>>
[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 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 lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> 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 here we want
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is :
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo :
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - 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
>>> was trying to find a workaround but i wasn't lucky. I also found that the
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
>>> escribió:
>>>
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 operators, but if I
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> 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 versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> 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 I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
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
> is says
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters
> which are separated by a , character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> 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 rewrite
[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 22:08:07 UTC+10 jn.pierr...@gmail.com wrote:
> 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 lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> 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 here we want
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is :
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo :
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - 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
>>> was trying to find a workaround but i wasn't lucky. I also found that the
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
>>> escribió:
>>>
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 operators, but if I
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> 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 versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> 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 I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
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
> is says
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters
> which are separated by a , character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> 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
[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 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 lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
>
>> 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 here we want
>> an AND :)
>>
>> So with a a tiny bit of tweaking the correct filter is :
>>
>> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Here's a live demo :
>>
>>
>> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
>> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>>
>>> - 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
>>> was trying to find a workaround but i wasn't lucky. I also found that the
>>> match operator doesn't support multiple parameters.
>>>
>>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
>>> escribió:
>>>
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 operators, but if I
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{
> [title[tid1],[tid2],[tid3]] }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> 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 versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> 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 I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
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
> is says
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters
> which are separated by a , character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> 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 rewrite your filter something like this (in
>> filtering transclusion)
[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 lundi 27 septembre 2021 à 10:58:01 UTC+2, Télumire a écrit :
> 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 here we want an
> AND :)
>
> So with a a tiny bit of tweaking the correct filter is :
>
> {{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Here's a live demo :
>
>
> https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
> Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
>
>> - 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
>> was trying to find a workaround but i wasn't lucky. I also found that the
>> match operator doesn't support multiple parameters.
>>
>> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
>> escribió:
>>
>>> 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 operators, but if I
read this correctly they can work on operators in *general*?
If general you may expect this to work ```{{{
[title[tid1],[tid2],[tid3]] }}}``` it does not.
or {{{ [all[current]get[caption],[description]] }}}``` it does not.
On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
> 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 versions of TW
> -e
> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>
>> 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 I asked if you tested this?
>>
>>
>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>
>>> 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
is says
* NEW IN: 5.1.23 Filter operators support multiple parameters which
are separated by a , character.*
*For example: [param1],[param2] or ,{param2}*
However as far as I can see only if such multiple parameters are
documented in the operator in question.
Tones
On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
> 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 rewrite your filter something like this (in filtering
> transclusion)
> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
> jn.pierr...@gmail.com escribió:
[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 here we want an
AND :)
So with a a tiny bit of tweaking the correct filter is :
{{{ [[Tag 1][Tag 2][Tag 3][Tag 4]tagging[]]
:filter[tags[]count[]compare:eq[4]] }}}
Here's a live demo :
https://Telumire.github.io/TW-tips/index.html#:%5B%5B4%20tags%20and%20only%20those%204%5D%5D%5B%5B3%20tags%20+%201%20other%5D%5D%5B%5B4%20tags%20and%20one%20more%5D%5D%5B%5BMultiple%20parameters%20separated%20by%20a%20%20,%20%20character%5D%5D
Le samedi 25 septembre 2021 à 18:00:37 UTC+2, Álvaro a écrit :
> - 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
> was trying to find a workaround but i wasn't lucky. I also found that the
> match operator doesn't support multiple parameters.
>
> El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones
> escribió:
>
>> 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 operators, but if I
>>> read this correctly they can work on operators in *general*?
>>>
>>> If general you may expect this to work ```{{{
>>> [title[tid1],[tid2],[tid3]] }}}``` it does not.
>>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>>
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 versions of TW
-e
On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
> 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 I asked if you tested this?
>
>
> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>
>> 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
>>> is says
>>>
>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which
>>> are separated by a , character.*
>>>
>>> *For example: [param1],[param2] or ,{param2}*
>>> However as far as I can see only if such multiple parameters are
>>> documented in the operator in question.
>>>
>>> Tones
>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>
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 rewrite your filter something like this (in filtering
transclusion)
{{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
:filter[tags[]count[]compare:eq[4]] }}}
Although maybe it be less understandble for you.
El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
jn.pierr...@gmail.com escribió:
> 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
> here...count[]]">Seen <> tiddlers with tags $tags$
> \end
>
> Sometimes,
[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 was
trying to find a workaround but i wasn't lucky. I also found that the match
operator doesn't support multiple parameters.
El sábado, 25 de septiembre de 2021 a las 16:30:26 UTC+2, TW Tones escribió:
> 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 operators, but if I
>> read this correctly they can work on operators in *general*?
>>
>> If general you may expect this to work ```{{{ [title[tid1],[tid2],[tid3]]
>> }}}``` it does not.
>> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
>> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>>
>>> 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 versions of TW
>>> -e
>>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>>
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 I asked if you tested this?
On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
> 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
>> is says
>>
>> * NEW IN: 5.1.23 Filter operators support multiple parameters which
>> are separated by a , character.*
>>
>> *For example: [param1],[param2] or ,{param2}*
>> However as far as I can see only if such multiple parameters are
>> documented in the operator in question.
>>
>> Tones
>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>
>>> 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 rewrite your filter something like this (in filtering
>>> transclusion)
>>> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> Although maybe it be less understandble for you.
>>>
>>>
>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
>>> jn.pierr...@gmail.com escribió:
>>>
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
here...count[]]">Seen <> tiddlers with tags $tags$
\end
Sometimes, this fun has you coding javascript filter operator.
Would this be the case here? I have not thought about it yet.
cheers,
Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com
a écrit :
> Me and my interest in brain age games, I couldn't help but play
> around with a filter to find all tiddlers that have all four
> specified
> tags, but only those four tags.
>
> You'll find three tiddlers in the attached json. Download the
> file, and drag into some TiddlyWiki instance (TiddlyWiki.com !) to
> take a
> gander.
>
> There are all kinds of ways to go about doing this sort of thing,
> with some filter operators maybe better suited, but I find the result
> a bit
> easier for me to understand (more logical to me, or maybe more
[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 operators, but if I
> read this correctly they can work on operators in *general*?
>
> If general you may expect this to work ```{{{ [title[tid1],[tid2],[tid3]]
> }}}``` it does not.
> or {{{ [all[current]get[caption],[description]] }}}``` it does not.
> On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
>
>> 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 versions of TW
>> -e
>> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>>
>>> 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 I asked if you tested this?
>>>
>>>
>>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>>
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
> is says
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters which
> are separated by a , character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> 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 rewrite your filter something like this (in filtering
>> transclusion)
>> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Although maybe it be less understandble for you.
>>
>>
>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
>> jn.pierr...@gmail.com escribió:
>>
>>> 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
>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>> \end
>>>
>>> Sometimes, this fun has you coding javascript filter operator. Would
>>> this be the case here? I have not thought about it yet.
>>>
>>> cheers,
>>>
>>>
>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>>> écrit :
>>>
Me and my interest in brain age games, I couldn't help but play
around with a filter to find all tiddlers that have all four specified
tags, but only those four tags.
You'll find three tiddlers in the attached json. Download the
file, and drag into some TiddlyWiki instance (TiddlyWiki.com !) to
take a
gander.
There are all kinds of ways to go about doing this sort of thing,
with some filter operators maybe better suited, but I find the result
a bit
easier for me to understand (more logical to me, or maybe more
self-explanatory, because of the way my brain works, I suppose.)
Maybe
just a difference between top-down view vs bottom-up view or something
...
Yeah, I find filters fun.
>>>
--
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/4c736a0d-c005-4a57-ad34-f9b678d787d5n%40googlegroups.com.
[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 ```{{{ [title[tid1],[tid2],[tid3]]
}}}``` it does not.
or {{{ [all[current]get[caption],[description]] }}}``` it does not.
On Sunday, 26 September 2021 at 00:18:58 UTC+10 Eric Shulman wrote:
> 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 versions of TW
> -e
> On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
>
>> 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 I asked if you tested this?
>>
>>
>> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>>
>>> 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
is says
* NEW IN: 5.1.23 Filter operators support multiple parameters which are
separated by a , character.*
*For example: [param1],[param2] or ,{param2}*
However as far as I can see only if such multiple parameters are
documented in the operator in question.
Tones
On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
> 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 rewrite your filter something like this (in filtering
> transclusion)
> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
> jn.pierr...@gmail.com escribió:
>
>> 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
>> here...count[]]">Seen <> tiddlers with tags $tags$
>> \end
>>
>> Sometimes, this fun has you coding javascript filter operator. Would
>> this be the case here? I have not thought about it yet.
>>
>> cheers,
>>
>>
>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>> écrit :
>>
>>> Me and my interest in brain age games, I couldn't help but play
>>> around with a filter to find all tiddlers that have all four specified
>>> tags, but only those four tags.
>>>
>>> You'll find three tiddlers in the attached json. Download the file,
>>> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a
>>> gander.
>>>
>>> There are all kinds of ways to go about doing this sort of thing,
>>> with some filter operators maybe better suited, but I find the result a
>>> bit
>>> easier for me to understand (more logical to me, or maybe more
>>> self-explanatory, because of the way my brain works, I suppose.) Maybe
>>> just a difference between top-down view vs bottom-up view or something
>>> ...
>>>
>>> Yeah, I find filters fun.
>>>
>>
--
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/30d92ecf-a87b-4d01-b96d-2bcb75bdcaadn%40googlegroups.com.
[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 versions of TW
-e
On Saturday, September 25, 2021 at 7:02:19 AM UTC-7 TW Tones wrote:
> 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 I asked if you tested this?
>
>
> On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
>
>> 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
>>> is says
>>>
>>> * NEW IN: 5.1.23 Filter operators support multiple parameters which are
>>> separated by a , character.*
>>>
>>> *For example: [param1],[param2] or ,{param2}*
>>> However as far as I can see only if such multiple parameters are
>>> documented in the operator in question.
>>>
>>> Tones
>>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>>
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 rewrite your filter something like this (in filtering transclusion)
{{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
:filter[tags[]count[]compare:eq[4]] }}}
Although maybe it be less understandble for you.
El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
jn.pierr...@gmail.com escribió:
> 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
> here...count[]]">Seen <> tiddlers with tags $tags$
> \end
>
> Sometimes, this fun has you coding javascript filter operator. Would
> this be the case here? I have not thought about it yet.
>
> cheers,
>
>
> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
> écrit :
>
>> Me and my interest in brain age games, I couldn't help but play
>> around with a filter to find all tiddlers that have all four specified
>> tags, but only those four tags.
>>
>> You'll find three tiddlers in the attached json. Download the file,
>> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a
>> gander.
>>
>> There are all kinds of ways to go about doing this sort of thing,
>> with some filter operators maybe better suited, but I find the result a
>> bit
>> easier for me to understand (more logical to me, or maybe more
>> self-explanatory, because of the way my brain works, I suppose.) Maybe
>> just a difference between top-down view vs bottom-up view or something
>> ...
>>
>> Yeah, I find filters fun.
>>
>
--
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/b5e785e5-7b0a-427d-9d29-46d3185e7aa6n%40googlegroups.com.
[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 I asked if you tested this?
On Saturday, 25 September 2021 at 22:11:48 UTC+10 Álvaro wrote:
> 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
>> is says
>>
>> * NEW IN: 5.1.23 Filter operators support multiple parameters which are
>> separated by a , character.*
>>
>> *For example: [param1],[param2] or ,{param2}*
>> However as far as I can see only if such multiple parameters are
>> documented in the operator in question.
>>
>> Tones
>> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>>
>>> 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 rewrite your filter something like this (in filtering transclusion)
>>> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
>>> :filter[tags[]count[]compare:eq[4]] }}}
>>>
>>> Although maybe it be less understandble for you.
>>>
>>>
>>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
>>> jn.pierr...@gmail.com escribió:
>>>
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
here...count[]]">Seen <> tiddlers with tags $tags$
\end
Sometimes, this fun has you coding javascript filter operator. Would
this be the case here? I have not thought about it yet.
cheers,
Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
écrit :
> Me and my interest in brain age games, I couldn't help but play around
> with a filter to find all tiddlers that have all four specified tags, but
> only those four tags.
>
> You'll find three tiddlers in the attached json. Download the file,
> and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a
> gander.
>
> There are all kinds of ways to go about doing this sort of thing, with
> some filter operators maybe better suited, but I find the result a bit
> easier for me to understand (more logical to me, or maybe more
> self-explanatory, because of the way my brain works, I suppose.) Maybe
> just a difference between top-down view vs bottom-up view or something ...
>
> Yeah, I find filters fun.
>
--
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/d59ad16a-d51c-4d14-be24-0394ef067cd1n%40googlegroups.com.
[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
> is says
>
> * NEW IN: 5.1.23 Filter operators support multiple parameters which are
> separated by a , character.*
>
> *For example: [param1],[param2] or ,{param2}*
> However as far as I can see only if such multiple parameters are
> documented in the operator in question.
>
> Tones
> On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
>
>> 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 rewrite your filter something like this (in filtering transclusion)
>> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Although maybe it be less understandble for you.
>>
>>
>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
>> jn.pierr...@gmail.com escribió:
>>
>>> 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
>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>> \end
>>>
>>> Sometimes, this fun has you coding javascript filter operator. Would
>>> this be the case here? I have not thought about it yet.
>>>
>>> cheers,
>>>
>>>
>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>>> écrit :
>>>
Me and my interest in brain age games, I couldn't help but play around
with a filter to find all tiddlers that have all four specified tags, but
only those four tags.
You'll find three tiddlers in the attached json. Download the file,
and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
There are all kinds of ways to go about doing this sort of thing, with
some filter operators maybe better suited, but I find the result a bit
easier for me to understand (more logical to me, or maybe more
self-explanatory, because of the way my brain works, I suppose.) Maybe
just a difference between top-down view vs bottom-up view or something ...
Yeah, I find filters fun.
>>>
--
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/c84aa10e-ef9b-47d3-a90f-f4100f3ef1b5n%40googlegroups.com.
[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 , character.*
*For example: [param1],[param2] or ,{param2}*
However as far as I can see only if such multiple parameters are documented
in the operator in question.
Tones
On Saturday, 25 September 2021 at 01:39:53 UTC+10 Álvaro wrote:
> 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 rewrite your filter something like this (in filtering transclusion)
> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
> jn.pierr...@gmail.com escribió:
>
>> 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
>> here...count[]]">Seen <> tiddlers with tags $tags$
>> \end
>>
>> Sometimes, this fun has you coding javascript filter operator. Would this
>> be the case here? I have not thought about it yet.
>>
>> cheers,
>>
>>
>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>> écrit :
>>
>>> Me and my interest in brain age games, I couldn't help but play around
>>> with a filter to find all tiddlers that have all four specified tags, but
>>> only those four tags.
>>>
>>> You'll find three tiddlers in the attached json. Download the file, and
>>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>>
>>> There are all kinds of ways to go about doing this sort of thing, with
>>> some filter operators maybe better suited, but I find the result a bit
>>> easier for me to understand (more logical to me, or maybe more
>>> self-explanatory, because of the way my brain works, I suppose.) Maybe
>>> just a difference between top-down view vs bottom-up view or something ...
>>>
>>> Yeah, I find filters fun.
>>>
>>
--
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/8b51d326-471c-4869-bdf9-6c5680937652n%40googlegroups.com.
[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 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" > > Yes, I tried with the tagging operator and I see that behaviour. > > El viernes, 24 de septiembre de 2021 a las 18:52:36 UTC+2, > jn.pierr...@gmail.com escribió: > >> 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 variable=occ filter="[[$tags$]tagging[] :filter]">Seen >> <> tiddlers with tags $tags$ >> >> \end >> >> But in fact the effect of tagging is "output: the titles of any tiddlers >> that carry ANY OF the input tags". Too bad for the instance. But I think a >> correction in the doc would be welcome. >> >> >> Le vendredi 24 septembre 2021 à 10:59:50 UTC+2, Jean-Pierre Rivière a >> écrit : >> >>> 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 >>> here...count[]]">Seen <> tiddlers with tags $tags$ >>> \end >>> >>> Sometimes, this fun has you coding javascript filter operator. Would >>> this be the case here? I have not thought about it yet. >>> >>> cheers, >>> >>> >>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a >>> écrit : >>> Me and my interest in brain age games, I couldn't help but play around with a filter to find all tiddlers that have all four specified tags, but only those four tags. You'll find three tiddlers in the attached json. Download the file, and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander. There are all kinds of ways to go about doing this sort of thing, with some filter operators maybe better suited, but I find the result a bit easier for me to understand (more logical to me, or maybe more self-explanatory, because of the way my brain works, I suppose.) Maybe just a difference between top-down view vs bottom-up view or something ... Yeah, I find filters fun. >>> -- 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/90e82076-b3c0-4296-ab56-050b2398414dn%40googlegroups.com.
[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" Yes, I tried with the tagging operator and I see that behaviour. El viernes, 24 de septiembre de 2021 a las 18:52:36 UTC+2, jn.pierr...@gmail.com escribió: > 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 variable=occ filter="[[$tags$]tagging[] :filter]">Seen <> > tiddlers with tags $tags$ > > \end > > But in fact the effect of tagging is "output: the titles of any tiddlers > that carry ANY OF the input tags". Too bad for the instance. But I think a > correction in the doc would be welcome. > > > Le vendredi 24 septembre 2021 à 10:59:50 UTC+2, Jean-Pierre Rivière a > écrit : > >> 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 >> here...count[]]">Seen <> tiddlers with tags $tags$ >> \end >> >> Sometimes, this fun has you coding javascript filter operator. Would this >> be the case here? I have not thought about it yet. >> >> cheers, >> >> >> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a >> écrit : >> >>> Me and my interest in brain age games, I couldn't help but play around >>> with a filter to find all tiddlers that have all four specified tags, but >>> only those four tags. >>> >>> You'll find three tiddlers in the attached json. Download the file, and >>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander. >>> >>> There are all kinds of ways to go about doing this sort of thing, with >>> some filter operators maybe better suited, but I find the result a bit >>> easier for me to understand (more logical to me, or maybe more >>> self-explanatory, because of the way my brain works, I suppose.) Maybe >>> just a difference between top-down view vs bottom-up view or something ... >>> >>> Yeah, I find filters fun. >>> >> -- 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/a7516220-72de-484d-adaf-b36aacd29c3cn%40googlegroups.com.
[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 variable=occ filter="[[$tags$]tagging[] :filter]">Seen <> tiddlers with tags $tags$ \end But in fact the effect of tagging is "output: the titles of any tiddlers that carry ANY OF the input tags". Too bad for the instance. But I think a correction in the doc would be welcome. Le vendredi 24 septembre 2021 à 10:59:50 UTC+2, Jean-Pierre Rivière a écrit : > 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 > here...count[]]">Seen <> tiddlers with tags $tags$ > \end > > Sometimes, this fun has you coding javascript filter operator. Would this > be the case here? I have not thought about it yet. > > cheers, > > > Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a > écrit : > >> Me and my interest in brain age games, I couldn't help but play around >> with a filter to find all tiddlers that have all four specified tags, but >> only those four tags. >> >> You'll find three tiddlers in the attached json. Download the file, and >> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander. >> >> There are all kinds of ways to go about doing this sort of thing, with >> some filter operators maybe better suited, but I find the result a bit >> easier for me to understand (more logical to me, or maybe more >> self-explanatory, because of the way my brain works, I suppose.) Maybe >> just a difference between top-down view vs bottom-up view or something ... >> >> Yeah, I find filters fun. >> > -- 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/45d80329-bd90-4d7f-b981-c090c9cc64e5n%40googlegroups.com.
[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 back and forth, like long scrolls up and down in a browser window, or
back and forward buttons on browsers, all cause dysfunction for this kid.
Thanks, Álvaro. You just helped me understand a little something there
about how I process things, or rather when I can't process things...
On Friday, September 24, 2021 at 1:28:11 PM UTC-3 Charlie Veniot wrote:
> 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 way when facing a Chinese food buffet,
> always holding up the line because of too many choices.
>
> Regardless, that is pretty awesome for normal folk who can bounce between
> the different ways the tag operator can be used.
>
>
> On Friday, September 24, 2021 at 12:39:53 PM UTC-3 Álvaro wrote:
>
>> 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 rewrite your filter something like this (in filtering transclusion)
>> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
>> :filter[tags[]count[]compare:eq[4]] }}}
>>
>> Although maybe it be less understandble for you.
>>
>>
>> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
>> jn.pierr...@gmail.com escribió:
>>
>>> 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
>>> here...count[]]">Seen <> tiddlers with tags $tags$
>>> \end
>>>
>>> Sometimes, this fun has you coding javascript filter operator. Would
>>> this be the case here? I have not thought about it yet.
>>>
>>> cheers,
>>>
>>>
>>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>>> écrit :
>>>
Me and my interest in brain age games, I couldn't help but play around
with a filter to find all tiddlers that have all four specified tags, but
only those four tags.
You'll find three tiddlers in the attached json. Download the file,
and drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
There are all kinds of ways to go about doing this sort of thing, with
some filter operators maybe better suited, but I find the result a bit
easier for me to understand (more logical to me, or maybe more
self-explanatory, because of the way my brain works, I suppose.) Maybe
just a difference between top-down view vs bottom-up view or something ...
Yeah, I find filters fun.
>>>
--
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/3ba7651c-a163-4b98-be43-ad9089a10209n%40googlegroups.com.
[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 way when facing a Chinese food buffet,
always holding up the line because of too many choices.
Regardless, that is pretty awesome for normal folk who can bounce between
the different ways the tag operator can be used.
On Friday, September 24, 2021 at 12:39:53 PM UTC-3 Álvaro wrote:
> 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 rewrite your filter something like this (in filtering transclusion)
> {{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
> :filter[tags[]count[]compare:eq[4]] }}}
>
> Although maybe it be less understandble for you.
>
>
> El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
> jn.pierr...@gmail.com escribió:
>
>> 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
>> here...count[]]">Seen <> tiddlers with tags $tags$
>> \end
>>
>> Sometimes, this fun has you coding javascript filter operator. Would this
>> be the case here? I have not thought about it yet.
>>
>> cheers,
>>
>>
>> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
>> écrit :
>>
>>> Me and my interest in brain age games, I couldn't help but play around
>>> with a filter to find all tiddlers that have all four specified tags, but
>>> only those four tags.
>>>
>>> You'll find three tiddlers in the attached json. Download the file, and
>>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>>
>>> There are all kinds of ways to go about doing this sort of thing, with
>>> some filter operators maybe better suited, but I find the result a bit
>>> easier for me to understand (more logical to me, or maybe more
>>> self-explanatory, because of the way my brain works, I suppose.) Maybe
>>> just a difference between top-down view vs bottom-up view or something ...
>>>
>>> Yeah, I find filters fun.
>>>
>>
--
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/0ce46048-5cfe-4fb3-b5b9-3d5367fcd007n%40googlegroups.com.
[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 rewrite your filter something like this (in filtering transclusion)
{{{ [tag[Tag 1]*,*[Tag 2],[Tag 3],[Tag 4]]
:filter[tags[]count[]compare:eq[4]] }}}
Although maybe it be less understandble for you.
El viernes, 24 de septiembre de 2021 a las 10:59:50 UTC+2,
jn.pierr...@gmail.com escribió:
> 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
> here...count[]]">Seen <> tiddlers with tags $tags$
> \end
>
> Sometimes, this fun has you coding javascript filter operator. Would this
> be the case here? I have not thought about it yet.
>
> cheers,
>
>
> Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a
> écrit :
>
>> Me and my interest in brain age games, I couldn't help but play around
>> with a filter to find all tiddlers that have all four specified tags, but
>> only those four tags.
>>
>> You'll find three tiddlers in the attached json. Download the file, and
>> drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander.
>>
>> There are all kinds of ways to go about doing this sort of thing, with
>> some filter operators maybe better suited, but I find the result a bit
>> easier for me to understand (more logical to me, or maybe more
>> self-explanatory, because of the way my brain works, I suppose.) Maybe
>> just a difference between top-down view vs bottom-up view or something ...
>>
>> Yeah, I find filters fun.
>>
>
--
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/42343ad0-6a2a-4b0f-a6d6-cc975235272fn%40googlegroups.com.
[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 here...count[]]">Seen <> tiddlers with tags $tags$ \end Sometimes, this fun has you coding javascript filter operator. Would this be the case here? I have not thought about it yet. cheers, Le vendredi 24 septembre 2021 à 03:54:34 UTC+2, cj.v...@gmail.com a écrit : > Me and my interest in brain age games, I couldn't help but play around > with a filter to find all tiddlers that have all four specified tags, but > only those four tags. > > You'll find three tiddlers in the attached json. Download the file, and > drag into some TiddlyWiki instance (TiddlyWiki.com !) to take a gander. > > There are all kinds of ways to go about doing this sort of thing, with > some filter operators maybe better suited, but I find the result a bit > easier for me to understand (more logical to me, or maybe more > self-explanatory, because of the way my brain works, I suppose.) Maybe > just a difference between top-down view vs bottom-up view or something ... > > Yeah, I find filters fun. > -- 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/097b783f-52c6-42f7-b0b5-9ed35c9198den%40googlegroups.com.
