Sortsub applies a filter in turn to each input title separately. The docs
do mention this I believe. So the input to the filter each time is a single
title.
Subfilter applies a filter once with the input being a title list of all
input titles.
On Friday, April 30, 2021 at 10:53:52 AM UTC+2 jn.pierr...@gmail.com wrote:
> Nestling, in such a way anyway, is something I had not thought about.
>
> In fact, this is only a part of the pipeline. Can I get back a united
> output afterwards? I'll experiment and if I'm at loss, I'll post again.
>
> A question remains for me: Why is "split + last" apparently working on so
> different data when called by sortsub or subfilter? Aren't they just
> calling a filter? What is causing the diffirence? I think it would be wise
> and good for me to understand what cause the difference in behavior of such
> similar patterns.
>
> regards,
>
> --
> Jean-Pierre
> Le vendredi 30 avril 2021 à 07:15:37 UTC+2, TW Tones a écrit :
>
>> Jean-Pierre;
>>
>> I am not sure about your requirement, but try these
>>
>> <$list filter="[enlist[a1^a2 b1^b2 c1^c2]]">
>> {{{ [<currentTiddler>split[^]first[]] }}}
>> </$list>
>> <hr>
>> <$list filter="[enlist[a1^a2 b1^b2 c1^c2]]">
>> <$list filter="[<currentTiddler>split[^]first[]]">
>>
>> </$list>
>> </$list>
>> <hr>
>> <$list filter="[enlist[a1^a2 b1^b2 c1^c3]split[^]]">
>>
>> </$list>
>> <hr>
>> <$list filter="[[a1^a2 b1^b2 c1^c3]split[ ]split[^]]">
>>
>> </$list>
>>
>> I was recently considering a similar problem, when someone was
>> questioning nesting list widgets, when I realised the $list with filters
>> can act as gosub, while, do until etc... so nesting them is by definition
>> sometimes a logical requirement depending what you are trying to achieve
>> with your filters. Nesting is not easy or possible in many cases with
>> triple curly braces.
>>
>> Regards
>> Tones
>>
>> On Friday, 30 April 2021 at 07:15:04 UTC+10 jn.pierr...@gmail.com wrote:
>>
>>> Toying with filters, I discovered that the split operator agglomerates
>>> its results when ist operates on successive titles.
>>>
>>> for instance : {{{ [enlist[a1^a2 b1^b2 c1^c2]split[^][]first[]] }}}
>>> results in a1 not in a1, b1, c1
>>>
>>> a sufilter dos not change anything:
>>>
>>> <$vars sf="[split[^]dump[]first[]]">
>>> {{{ [enlist[a1^a2 b1^b2 c1^c2]subfilter<sf>] }}}
>>> </$vars>
>>>
>>> In fact, in each case, after split, the filter values are a1, a2, b1,
>>> b2, c1, c2.
>>>
>>> could there be a way to have [a1, a2], [b1, b2], [c1, c2]
>>> from enlist[a1^a2 b1^b2 c1^c2] ?
>>>
>>> let's use sortsub and a little input set to see that what I am asking
>>> for may not be that impossible.
>>>
>>> <$vars sf="[split[^]dump[]last[]]">
>>> {{{ [enlist[a1^22 b1^28 c1^14]sortsub<sf>] }}}
>>> </$vars>
>>>
>>> reults in c1^14, a1^22, b1^28
>>>
>>> which demonstrate that here split produces things like c1, 14 on which
>>> split act upon. exactly what I wanted to achieve with subfilter.
>>>
>>> --
>>> 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/db9f9535-8783-4cdf-8b10-874fee0482een%40googlegroups.com.
