[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[David]

I'll think about that.  Sometimes I may want to select and copy the text.  
I'll have to think of which I want to do more.

Thanks!!

On Tuesday, May 24, 2022 at 12:27:54 PM UTC-4 Eric Shulman wrote:

> One final tweak to the code:
> instead of:
> ```
> <$checkbox index=<> checked="1" unchecked="0"/><>
> ```
> I suggest putting the item text within the body of the $checkbox widget, 
> like this:
> ```
> <$checkbox index=<> checked="1" unchecked="0"> <> 
> 
> ```
> This allows you to click on the item text to toggle the checkbox.
>
> -e
> On Tuesday, May 24, 2022 at 9:12:15 AM UTC-7 David wrote:
>
>> Thanks!
>>
>> That is perfect!. I think I have several other pages that can enjoy this 
>> kind of feature, as well.
>>
>> On Tuesday, May 24, 2022 at 8:38:12 AM UTC-4 Eric Shulman wrote:
>>
>>> On Tuesday, May 24, 2022 at 4:36:35 AM UTC-7 David wrote:
>>>
 ```
 <$list 
 filter="[indexes[]search:title:literal[Vegas]sort[]]" 
 variable=item>
 ```

>>> But it seems your code snippet is not working with the variable/field in 
 there.  It works fine when I put some static text there, though, as seen 
 in 
 my line above.

>>>
>>> The problem is due to the surrounding `<$tiddler tiddler="Dictionary 
>>> Tiddler">... ` widget.
>>> Because of this, the reference to `{!!searchText}` is looking in 
>>> "Dictionary Tiddler" for the field contents.
>>> One way around this is to remove the `$tiddler` widget and hard-code the 
>>> "Dictionary Tiddler" title, like this:
>>> ```
>>> <$list filter="[[Dictionary 
>>> Tiddler]indexes[]search:title:literal{!!searchText}sort[]]" variable=item>
>>> <$checkbox tiddler="Dictionary Tiddler" index=<> checked="1" 
>>> unchecked="0"/>
>>> <>
>>> 
>>> ```
>>> This allows the `{!!searchText}` reference to point to a field in the 
>>> tiddler containing the `<$list>` widget, rather than the "Dictionary 
>>> Tiddler" itself.
>>>
>>> However... if the intention is to eventually enable lookups using 
>>> different Dictionary Tiddlers, then the following code may be more useful:
>>> ```
>>> <$edit-text field="searchText"/>
>>> <$select field="dictionary">
>>>Dictionary Tiddler
>>>Another Dictionary
>>>Some Other Dictionary
>>>etc...
>>> 
>>> 
>>> <$let searchText={{!!searchText}}>
>>> <$tiddler tiddler={{!!dictionary}}>
>>> <$list 
>>> filter="[all[current]indexes[]search:title:literalsort[]]" 
>>> variable=item>
>>>
>>> <$checkbox index=<> checked="1" unchecked="0"/>
>>> <>
>>> 
>>> 
>>> 
>>> ```
>>> Basically, this sets a variable to the value of the searchText field 
>>> before using `$tiddler` to change the current tiddler,
>>> and then uses the value of that variable in the filter syntax.  It also 
>>> lets you select a dictionary tiddler title from a
>>> droplist input, and then uses that title in the `$tiddler` widget, so 
>>> that the lookup points to another dictionary while
>>> still using the searchText input from the current tiddler.
>>>
>>> enjoy,
>>> -e
>>>
>>

-- 
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/a6e41a9b-8423-4b69-93d6-da535e3bfc3bn%40googlegroups.com.

[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[Eric Shulman]

One final tweak to the code:
instead of:
```
<$checkbox index=<> checked="1" unchecked="0"/><>
```
I suggest putting the item text within the body of the $checkbox widget, 
like this:
```
<$checkbox index=<> checked="1" unchecked="0"> <> 

```
This allows you to click on the item text to toggle the checkbox.

-e
On Tuesday, May 24, 2022 at 9:12:15 AM UTC-7 David wrote:

> Thanks!
>
> That is perfect!. I think I have several other pages that can enjoy this 
> kind of feature, as well.
>
> On Tuesday, May 24, 2022 at 8:38:12 AM UTC-4 Eric Shulman wrote:
>
>> On Tuesday, May 24, 2022 at 4:36:35 AM UTC-7 David wrote:
>>
>>> ```
>>> <$list 
>>> filter="[indexes[]search:title:literal[Vegas]sort[]]" 
>>> variable=item>
>>> ```
>>>
>> But it seems your code snippet is not working with the variable/field in 
>>> there.  It works fine when I put some static text there, though, as seen in 
>>> my line above.
>>>
>>
>> The problem is due to the surrounding `<$tiddler tiddler="Dictionary 
>> Tiddler">... ` widget.
>> Because of this, the reference to `{!!searchText}` is looking in 
>> "Dictionary Tiddler" for the field contents.
>> One way around this is to remove the `$tiddler` widget and hard-code the 
>> "Dictionary Tiddler" title, like this:
>> ```
>> <$list filter="[[Dictionary 
>> Tiddler]indexes[]search:title:literal{!!searchText}sort[]]" variable=item>
>> <$checkbox tiddler="Dictionary Tiddler" index=<> checked="1" 
>> unchecked="0"/>
>> <>
>> 
>> ```
>> This allows the `{!!searchText}` reference to point to a field in the 
>> tiddler containing the `<$list>` widget, rather than the "Dictionary 
>> Tiddler" itself.
>>
>> However... if the intention is to eventually enable lookups using 
>> different Dictionary Tiddlers, then the following code may be more useful:
>> ```
>> <$edit-text field="searchText"/>
>> <$select field="dictionary">
>>Dictionary Tiddler
>>Another Dictionary
>>Some Other Dictionary
>>etc...
>> 
>> 
>> <$let searchText={{!!searchText}}>
>> <$tiddler tiddler={{!!dictionary}}>
>> <$list 
>> filter="[all[current]indexes[]search:title:literalsort[]]" 
>> variable=item>
>>
>> <$checkbox index=<> checked="1" unchecked="0"/>
>> <>
>> 
>> 
>> 
>> ```
>> Basically, this sets a variable to the value of the searchText field 
>> before using `$tiddler` to change the current tiddler,
>> and then uses the value of that variable in the filter syntax.  It also 
>> lets you select a dictionary tiddler title from a
>> droplist input, and then uses that title in the `$tiddler` widget, so 
>> that the lookup points to another dictionary while
>> still using the searchText input from the current tiddler.
>>
>> enjoy,
>> -e
>>
>

-- 
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/b573c5d5-0049-4964-b267-8b4e4f5d46e7n%40googlegroups.com.

[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[David]

Thanks!

That is perfect!. I think I have several other pages that can enjoy this 
kind of feature, as well.

On Tuesday, May 24, 2022 at 8:38:12 AM UTC-4 Eric Shulman wrote:

> On Tuesday, May 24, 2022 at 4:36:35 AM UTC-7 David wrote:
>
>> ```
>> <$list 
>> filter="[indexes[]search:title:literal[Vegas]sort[]]" 
>> variable=item>
>> ```
>>
> But it seems your code snippet is not working with the variable/field in 
>> there.  It works fine when I put some static text there, though, as seen in 
>> my line above.
>>
>
> The problem is due to the surrounding `<$tiddler tiddler="Dictionary 
> Tiddler">... ` widget.
> Because of this, the reference to `{!!searchText}` is looking in 
> "Dictionary Tiddler" for the field contents.
> One way around this is to remove the `$tiddler` widget and hard-code the 
> "Dictionary Tiddler" title, like this:
> ```
> <$list filter="[[Dictionary 
> Tiddler]indexes[]search:title:literal{!!searchText}sort[]]" variable=item>
> <$checkbox tiddler="Dictionary Tiddler" index=<> checked="1" 
> unchecked="0"/>
> <>
> 
> ```
> This allows the `{!!searchText}` reference to point to a field in the 
> tiddler containing the `<$list>` widget, rather than the "Dictionary 
> Tiddler" itself.
>
> However... if the intention is to eventually enable lookups using 
> different Dictionary Tiddlers, then the following code may be more useful:
> ```
> <$edit-text field="searchText"/>
> <$select field="dictionary">
>Dictionary Tiddler
>Another Dictionary
>Some Other Dictionary
>etc...
> 
> 
> <$let searchText={{!!searchText}}>
> <$tiddler tiddler={{!!dictionary}}>
> <$list 
> filter="[all[current]indexes[]search:title:literalsort[]]" 
> variable=item>
>
> <$checkbox index=<> checked="1" unchecked="0"/>
> <>
> 
> 
> 
> ```
> Basically, this sets a variable to the value of the searchText field 
> before using `$tiddler` to change the current tiddler,
> and then uses the value of that variable in the filter syntax.  It also 
> lets you select a dictionary tiddler title from a
> droplist input, and then uses that title in the `$tiddler` widget, so that 
> the lookup points to another dictionary while
> still using the searchText input from the current tiddler.
>
> enjoy,
> -e
>

-- 
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/61995960-bea2-48a3-a12e-be205e5e424en%40googlegroups.com.

[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[Eric Shulman]

On Tuesday, May 24, 2022 at 4:36:35 AM UTC-7 David wrote:

> ```
> <$list 
> filter="[indexes[]search:title:literal[Vegas]sort[]]" 
> variable=item>
> ```
> But it seems your code snippet is not working with the variable/field in 
> there.  It works fine when I put some static text there, though, as seen in 
> my line above.
>

The problem is due to the surrounding `<$tiddler tiddler="Dictionary 
Tiddler">... ` widget.
Because of this, the reference to `{!!searchText}` is looking in 
"Dictionary Tiddler" for the field contents.
One way around this is to remove the `$tiddler` widget and hard-code the 
"Dictionary Tiddler" title, like this:
```
<$list filter="[[Dictionary 
Tiddler]indexes[]search:title:literal{!!searchText}sort[]]" variable=item>
<$checkbox tiddler="Dictionary Tiddler" index=<> checked="1" 
unchecked="0"/>
<>

```
This allows the `{!!searchText}` reference to point to a field in the 
tiddler containing the `<$list>` widget, rather than the "Dictionary 
Tiddler" itself.

However... if the intention is to eventually enable lookups using different 
Dictionary Tiddlers, then the following code may be more useful:
```
<$edit-text field="searchText"/>
<$select field="dictionary">
   Dictionary Tiddler
   Another Dictionary
   Some Other Dictionary
   etc...


<$let searchText={{!!searchText}}>
<$tiddler tiddler={{!!dictionary}}>
<$list 
filter="[all[current]indexes[]search:title:literalsort[]]" 
variable=item>
<$checkbox index=<> checked="1" unchecked="0"/>
<>



```
Basically, this sets a variable to the value of the searchText field before 
using `$tiddler` to change the current tiddler,
and then uses the value of that variable in the filter syntax.  It also 
lets you select a dictionary tiddler title from a
droplist input, and then uses that title in the `$tiddler` widget, so that 
the lookup points to another dictionary while
still using the searchText input from the current tiddler.

enjoy,
-e

-- 
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/f819aafb-7fc8-452a-ab9c-26b8ca5b7e29n%40googlegroups.com.

[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[David]

```
<$list 
filter="[indexes[]search:title:literal[Vegas]sort[]]" 
variable=item>
```

Thanks for replying.  I'll note that other forum for future questions.

But it seems your code snippet is not working with the variable/field in 
there.  It works fine when I put some static text there, though, as seen in 
my line above.

On Monday, May 23, 2022 at 9:34:47 PM UTC-4 Eric Shulman wrote:

> On Monday, May 23, 2022 at 6:04:21 PM UTC-7 David wrote:
> ```
> <$list filter="[all[current]indexes[]containssort[]]" 
> variable=item>
> ```
>
> `contains>` is incorrect for two reasons:
>
> * The field reference `!!searchText` should enclosed with curly braces: 
> `{!!searchText}`, not angle brackets.  Remember: the delimiters around 
> filter operands correspond to the type of operand: square brackets are for 
> literal text, angle brackets are for variable names, curly braces are for 
> tiddler field references.
> * The `contains` operator is used to search within items of a list field.  
> To search the items in the current filter input, use the `search:title` 
> operator.  Note that, although the input items are actually indexes, for 
> the purposes of the `search` operator, they are handled as a list of 
> "titles".
> * Also note that, while `all[current]` is valid usage here, you could use 
> `` instead.  There's no semantic difference, but 
> `` is *slightly* more efficient than `all[current]`, since 
> it doesn't have to parse the "current" operand to retrieve the tiddler 
> title.
>
> Thus, your filter should be:
> ```
> <$list 
> filter="[indexes[]search:title:literal{!!searchText}sort[]]" 
> variable=item>
> ```
>
> enjoy,
> -e
>
> P.S. I recommend visiting https://talk.tiddlywiki.org/ for a more active 
> group in which to ask questions.
>

-- 
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/b6b88911-c2d3-4a18-baff-9b25897d63a7n%40googlegroups.com.

[tw5] Re: Filter display of Dictionary List items based on tiddler's field??

[Eric Shulman]

On Monday, May 23, 2022 at 6:04:21 PM UTC-7 David wrote:
```
<$list filter="[all[current]indexes[]containssort[]]" 
variable=item>
```

`contains>` is incorrect for two reasons:

* The field reference `!!searchText` should enclosed with curly braces: 
`{!!searchText}`, not angle brackets.  Remember: the delimiters around 
filter operands correspond to the type of operand: square brackets are for 
literal text, angle brackets are for variable names, curly braces are for 
tiddler field references.
* The `contains` operator is used to search within items of a list field.  
To search the items in the current filter input, use the `search:title` 
operator.  Note that, although the input items are actually indexes, for 
the purposes of the `search` operator, they are handled as a list of 
"titles".
* Also note that, while `all[current]` is valid usage here, you could use 
`` instead.  There's no semantic difference, but 
`` is *slightly* more efficient than `all[current]`, since 
it doesn't have to parse the "current" operand to retrieve the tiddler 
title.

Thus, your filter should be:
```
<$list 
filter="[indexes[]search:title:literal{!!searchText}sort[]]" 
variable=item>
```

enjoy,
-e

P.S. I recommend visiting https://talk.tiddlywiki.org/ for a more active 
group in which to ask questions.

-- 
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/103a73be-5fb2-45fa-a0a6-6faa543ee4e8n%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[thor...@gmail.com]

I am satisfied with the  `<$vars tagList={{{ 
[enlist{$:/temp/tagSearch}sort[]join[,]] }}}>` solution. I may have other 
questions to make my custom search tiddler look nicer, but that can be a 
separate thread if needed. Tyvm again for the help!

On Thursday, September 23, 2021 at 9:06:51 PM UTC-4 Eric Shulman wrote:

> On Thursday, September 23, 2021 at 3:57:35 PM UTC-7 thor...@gmail.com 
> wrote:
>
>> How might I make this searching tiddler more robust in the presence of 
>> "tags with spaces", since I also use spaces to delimit tags in the 
>> `edit-text`?
>>
>
> The problem is the use of
> `<$set name="tagList" filter="[enlist{$:/temp/tagSearch}sort[]join[,]]">`
>
> Let’s say you entered “foo [[bar baz]]” (i.e., two tags, “foo” and “bar 
> baz”).
>
> Then, you might expect the results of the above $set widget to be “foo,bar 
> baz”. However, because this string contains a space, the $set widget 
> *automatically 
> encloses the output in double square brackets*. Thus, the actual result 
> is “[[foo,bar baz]]”. Then, when you use `match` later on, it 
> expects those square brackets to be part of the literal string match.
>
> The solution is to use $vars with a “filtered transclusion” for the value, 
> instead of $set, like this:
> `<$vars tagList={{{ [enlist{$:/temp/tagSearch}sort[]join[,]] }}}>`
> Then, tagList will be “foo,bar baz”, as you intended.
>
> Alternatively, you *can* use $set, by adding “select=0” as an extra 
> parameter, like this:
> `<$set name="tagList" filter="[enlist{$:/temp/tagSearch}sort[]join[,]]" 
> select=0>`
> This tells the $set widget to only return the first list item (i.e., 
> item #0), without adding any square brackets.
> -e
>

-- 
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/3d9522b5-d61a-459e-ab3f-85c7452fd766n%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

On Thursday, September 23, 2021 at 3:57:35 PM UTC-7 thor...@gmail.com wrote:

> How might I make this searching tiddler more robust in the presence of 
> "tags with spaces", since I also use spaces to delimit tags in the 
> `edit-text`?
>

The problem is the use of
`<$set name="tagList" filter="[enlist{$:/temp/tagSearch}sort[]join[,]]">`

Let’s say you entered “foo [[bar baz]]” (i.e., two tags, “foo” and “bar 
baz”).

Then, you might expect the results of the above $set widget to be “foo,bar 
baz”. However, because this string contains a space, the $set widget 
*automatically 
encloses the output in double square brackets*. Thus, the actual result is 
“[[foo,bar baz]]”. Then, when you use `match` later on, it expects 
those square brackets to be part of the literal string match.

The solution is to use $vars with a “filtered transclusion” for the value, 
instead of $set, like this:
`<$vars tagList={{{ [enlist{$:/temp/tagSearch}sort[]join[,]] }}}>`
Then, tagList will be “foo,bar baz”, as you intended.

Alternatively, you *can* use $set, by adding “select=0” as an extra 
parameter, like this:
`<$set name="tagList" filter="[enlist{$:/temp/tagSearch}sort[]join[,]]" 
select=0>`
This tells the $set widget to only return the first list item (i.e., 
item #0), without adding any square brackets.
-e

-- 
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/4bc9490a-758e-4882-b3fe-112cb45c3bbdn%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

>
> On Thursday, September 23, 2021 at 6:07:22 PM UTC-4 thor...@gmail.com 
> wrote:
>
>> I just learned that list widgets can be nested; why does the above list 
>> return "the titles of the 10 tiddlers with the appropriate tags rather than 
>> printing the string "playground,rust,test,two words" 10 times, since the 
>> output of `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two 
>> words]]` for a given tiddler will be either no match or 
>> "playground,rust,test,two words"?
>>
>
Because the inner $list widget uses variable="has_matching_tags", the 
results of the filter does not change the value of currentTiddler as set by 
the outer $list widget and <$link/> outputs the titles of the matched 
tiddlers instead of the text “playground,rust,test,two words”

-e

-- 
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/81886e57-70ec-47f1-a9c4-665ae861de26n%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[thor...@gmail.com]

Based on our discussion so far, I've created a tiddler for doing "exact tag 
matches". Unfortunately, it seems to fall over tags with multiple 
words/spaces in it. How might I make this searching tiddler more robust in 
the presence of "tags with spaces", since I also use spaces to delimit tags 
in the `edit-text`?

On Thursday, September 23, 2021 at 6:07:22 PM UTC-4 thor...@gmail.com wrote:

> ```
> <$list filter="[all[]]">
><$list 
> filter="[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]" 
> variable="has_matching_tags">
>   <$link/>
>
> 
> ```
>
> So, this list does what I want and thus answers the question. However, I 
> think I misunderstand something fundamental about lists and filters.
>
> Filters (typically) take in a set of tiddlers and return a set of tiddlers 
> as their output, per the documentation 
> . 
>
> In the case of `enlist{!!tags}sort[]join[,]` by itself, the filter output 
> will be "the current tiddler's tags treated as tiddlers, regardless of 
> whether they exist or not". And running `match[playground,rust,test,two 
> words]` as a subsequent step for a single tiddler will either return no 
> match, or will return "playground,rust,test,two words" (the match docs 
>  say "potentially 
> including duplicates", but I couldn't get that to trigger for e.g. `{{{a 
> [[b c]] [[b c]] +[match[b c]]}}}`).
>
> I just learned that list widgets can be nested; why does the above list 
> return "the titles of the 10 tiddlers with the appropriate tags rather than 
> printing the string "playground,rust,test,two words" 10 times, since the 
> output of `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two 
> words]]` for a given tiddler will be either no match or 
> "playground,rust,test,two words"?
>
> On Wednesday, September 22, 2021 at 9:00:20 AM UTC-4 Eric Shulman wrote:
>
>> On Wednesday, September 22, 2021 at 5:23:57 AM UTC-7 cj.v...@gmail.com 
>> wrote:
>>
>>> [tag[playground]tag[rust]tag[test]tag[two words]] 
>>>
>>
>> The OP goal was to find tiddlers that have all the specified tags, but 
>> ONLY those tags and no others.
>> The problem is that the filter you suggest will also match tiddlers that 
>> have *other* tags in addition to the four tags specified.
>>
>> -e
>>
>

-- 
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/8a964750-9410-4ef3-ab63-523fd3a20a66n%40googlegroups.com.


Exact Tag Search.json
Description: application/json

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[thor...@gmail.com]

```
<$list filter="[all[]]">
   <$list 
filter="[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]" 
variable="has_matching_tags">
  <$link/>
   

```

So, this list does what I want and thus answers the question. However, I 
think I misunderstand something fundamental about lists and filters.

Filters (typically) take in a set of tiddlers and return a set of tiddlers 
as their output, per the documentation 
. 

In the case of `enlist{!!tags}sort[]join[,]` by itself, the filter output 
will be "the current tiddler's tags treated as tiddlers, regardless of 
whether they exist or not". And running `match[playground,rust,test,two 
words]` as a subsequent step for a single tiddler will either return no 
match, or will return "playground,rust,test,two words" (the match docs 
 say "potentially 
including duplicates", but I couldn't get that to trigger for e.g. `{{{a 
[[b c]] [[b c]] +[match[b c]]}}}`).

I just learned that list widgets can be nested; why does the above list 
return "the titles of the 10 tiddlers with the appropriate tags rather than 
printing the string "playground,rust,test,two words" 10 times, since the 
output of `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two 
words]]` for a given tiddler will be either no match or 
"playground,rust,test,two words"?

On Wednesday, September 22, 2021 at 9:00:20 AM UTC-4 Eric Shulman wrote:

> On Wednesday, September 22, 2021 at 5:23:57 AM UTC-7 cj.v...@gmail.com 
> wrote:
>
>> [tag[playground]tag[rust]tag[test]tag[two words]] 
>>
>
> The OP goal was to find tiddlers that have all the specified tags, but 
> ONLY those tags and no others.
> The problem is that the filter you suggest will also match tiddlers that 
> have *other* tags in addition to the four tags specified.
>
> -e
>

-- 
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/d16672a9-5b52-479d-83bf-bda261aee24an%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

On Wednesday, September 22, 2021 at 5:23:57 AM UTC-7 cj.v...@gmail.com 
wrote:

> [tag[playground]tag[rust]tag[test]tag[two words]] 
>

The OP goal was to find tiddlers that have all the specified tags, but ONLY 
those tags and no others.
The problem is that the filter you suggest will also match tiddlers that 
have *other* tags in addition to the four tags specified.

-e

-- 
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/6bb97930-6de7-48da-9f4b-b399304a89c3n%40googlegroups.com.

Re: [tw5] Re: Filter tiddlers with exactly one tag.

[CJ Veniot]

[tag[playground]tag[rust]tag[test]tag[two words]]

On Wed, Sep 22, 2021 at 2:52 AM thor...@gmail.com 
wrote:

> I tried to experiment with
> `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]` and
> uploaded the results. `[enlist{!!tags}sort[]join[,]]` returns the same
> thing as `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two
> words]]` from my testing, so I'm not exactly sure what the match is for.
>
> I'm not sure how to combine it with another filter to actually return a
> list of "these tiddlers with exactly these 4 tags". Is there a way to
> do "these tiddlers with exactly these 4 tags and nothing else" filter
> without using a variable (so I can put it into advanced search)?
>
> On Tuesday, September 21, 2021 at 11:29:16 PM UTC-4 Eric Shulman wrote:
>
>> On Tuesday, September 21, 2021 at 7:41:06 PM UTC-7 thor...@gmail.com
>> wrote:
>>
>>> I have 10 tiddlers tagged with both `playground` and `rust`
>>> (`[tag[rust]tag[playground]]` returns them all, but _pretend_ that I could
>>> have tiddlers with more than just two tags). In advanced search,
>>> `[field:tags[rust playground]]` returns 3 matches, and
>>> `[field:tags[playground rust]]` returns 7 matches. Meaning that Tiddlywiki
>>> knows the order that I put tags in even though they are sorted when
>>> displayed in the browser. Is there a way to return "exactly these 2 or 3
>>> etc" tags without having to try all permutations of tags?
>>>
>>
>> Let's assume you have FOUR tags: "rust", "playground", "two words", and
>> "test"
>>
>> Try this filter:
>> `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]`
>>
>> Notes:
>> * If a tag contains a space, it is stored with square brackets, e.g.,
>> `[[two words]]`
>> * enlist{!!tags} gets the individual tags as separate items, and any
>> square brackets are removed (but "two words" will still be ONE tag)
>> * next, sort them alphabetically, in ascending order
>> * then join the tags with a comma as a delimiter
>> * and match with literal text containing commas
>>
>> Let me know how it goes.
>>
>> enjoy,
>> -e
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/oT5RtR8S1Gg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/f6c21926-6a5e-4c8f-870d-dc7edbe5f4f3n%40googlegroups.com
> 
> .
>

-- 
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/CAMu8EfN5FBbef2UvvJXmhK-5gQAzBzoePPrjmNTS95TiuLPB-Q%40mail.gmail.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

On Tuesday, September 21, 2021 at 10:52:04 PM UTC-7 thor...@gmail.com wrote:

> I tried to experiment with 
> `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]` and 
> uploaded the results. `[enlist{!!tags}sort[]join[,]]` returns the same 
> thing as `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two 
> words]]` from my testing, so I'm not exactly sure what the match is for.
>

The filter I provided assumes that it is contained within a tiddler that 
has tags.  The purpose of the `match[playground,rust,test,two words]` 
filter syntax is to test the result of the filter to see if it has all the 
desired tags.

However... you can't use $:/AdvancedSearch to return "a list of tiddlers 
with exactly these 4 tags", because that needs two nested $list widgets, 
where the outer $list gets all the tiddler titles, and the inner $list 
checks each tiddler for the matching set of tags.  Thus, to list all 
tiddlers that have the desired tags, you can put the following into a 
tiddler:
```
<$list filter="[all[]]">
   <$list 
filter="[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]" 
variable="has_matching_tags">
  <$link/>
   

```
Note the use of the variable in the inner $list.  This preserves the value 
of "currentTiddler" that is assigned by the outer $list so that it can be 
output by the $link widget.

-e


-- 
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/fb36cc56-d93d-4d63-9d8a-164844c12c42n%40googlegroups.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[thor...@gmail.com]

I tried to experiment with 
`[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]` and 
uploaded the results. `[enlist{!!tags}sort[]join[,]]` returns the same 
thing as `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two 
words]]` from my testing, so I'm not exactly sure what the match is for.

I'm not sure how to combine it with another filter to actually return a 
list of "these tiddlers with exactly these 4 tags". Is there a way to 
do "these tiddlers with exactly these 4 tags and nothing else" filter 
without using a variable (so I can put it into advanced search)?

On Tuesday, September 21, 2021 at 11:29:16 PM UTC-4 Eric Shulman wrote:

> On Tuesday, September 21, 2021 at 7:41:06 PM UTC-7 thor...@gmail.com 
> wrote:
>
>> I have 10 tiddlers tagged with both `playground` and `rust` 
>> (`[tag[rust]tag[playground]]` returns them all, but _pretend_ that I could 
>> have tiddlers with more than just two tags). In advanced search, 
>> `[field:tags[rust playground]]` returns 3 matches, and 
>> `[field:tags[playground rust]]` returns 7 matches. Meaning that Tiddlywiki 
>> knows the order that I put tags in even though they are sorted when 
>> displayed in the browser. Is there a way to return "exactly these 2 or 3 
>> etc" tags without having to try all permutations of tags?
>>
>  
> Let's assume you have FOUR tags: "rust", "playground", "two words", and 
> "test"
>
> Try this filter:
> `[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]`
>
> Notes:
> * If a tag contains a space, it is stored with square brackets, e.g., 
> `[[two words]]`
> * enlist{!!tags} gets the individual tags as separate items, and any 
> square brackets are removed (but "two words" will still be ONE tag)
> * next, sort them alphabetically, in ascending order
> * then join the tags with a comma as a delimiter
> * and match with literal text containing commas
>
> Let me know how it goes.
>
> enjoy,
> -e
>

-- 
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/f6c21926-6a5e-4c8f-870d-dc7edbe5f4f3n%40googlegroups.com.


Test Tiddler.json
Description: application/json

[tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

On Tuesday, September 21, 2021 at 7:41:06 PM UTC-7 thor...@gmail.com wrote:

> I have 10 tiddlers tagged with both `playground` and `rust` 
> (`[tag[rust]tag[playground]]` returns them all, but _pretend_ that I could 
> have tiddlers with more than just two tags). In advanced search, 
> `[field:tags[rust playground]]` returns 3 matches, and 
> `[field:tags[playground rust]]` returns 7 matches. Meaning that Tiddlywiki 
> knows the order that I put tags in even though they are sorted when 
> displayed in the browser. Is there a way to return "exactly these 2 or 3 
> etc" tags without having to try all permutations of tags?
>
 
Let's assume you have FOUR tags: "rust", "playground", "two words", and 
"test"

Try this filter:
`[enlist{!!tags}sort[]join[,]match[playground,rust,test,two words]]`

Notes:
* If a tag contains a space, it is stored with square brackets, e.g., 
`[[two words]]`
* enlist{!!tags} gets the individual tags as separate items, and any square 
brackets are removed (but "two words" will still be ONE tag)
* next, sort them alphabetically, in ascending order
* then join the tags with a comma as a delimiter
* and match with literal text containing commas

Let me know how it goes.

enjoy,
-e

-- 
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/a27256ee-43a7-4029-8bee-73d89d16af06n%40googlegroups.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[thor...@gmail.com]

`<$list 
filter="[field:tags[technical_todo]]"><>`

I'd like to add: this works beautifully for my use case as described. I'd 
like to extend the use case however, and I'm not sure this filter works 
as-is.

I have 10 tiddlers tagged with both `playground` and `rust` 
(`[tag[rust]tag[playground]]` returns them all, but _pretend_ that I could 
have tiddlers with more than just two tags). In advanced search, 
`[field:tags[rust playground]]` returns 3 matches, and 
`[field:tags[playground rust]]` returns 7 matches. Meaning that Tiddlywiki 
knows the order that I put tags in even though they are sorted when 
displayed in the browser. Is there a way to return "exactly these 2 or 3 
etc" tags without having to try all permutations of tags?

On Tuesday, September 21, 2021 at 4:49:17 PM UTC-4 cj.v...@gmail.com wrote:

> That *is* short, sweet and nice.  I do enjoy.
>
> However, am I correct in saying that this only works if tags are one word 
> or CamelCase words?
>
> *(I always use spaces in my multi-word tags because I find that easier to 
> read.  And they wind up double-bracketed by TiddlyWiki in the tags fields.)*
>
> On Tuesday, September 21, 2021 at 5:24:41 AM UTC-3 Eric Shulman wrote:
>
>> On Monday, September 20, 2021 at 7:38:43 PM UTC-7 thor...@gmail.com 
>> wrote:
>>
>>> ...is there a shorthand to only output those tiddlers with _exactly_ the 
>>> one tag I'm requesting
>>>
>>
>> Even though the "tags" field contains a list of tiddler titles, it is 
>> also just a simple text value and you can use the `fields:tags[...]` filter 
>> to look for a specific literal value in the field, without it as a list.
>>
>> `<$list 
>> filter="[field:tags[technical_todo]]"><>`
>> will give the results you want, without a lot of messy "counting" and 
>> such.
>>
>> enjoy,
>> -e
>>
>>

-- 
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/6d017458-c822-4d30-b5dc-ff185a1eb653n%40googlegroups.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[Charlie Veniot]

That *is* short, sweet and nice.  I do enjoy.

However, am I correct in saying that this only works if tags are one word 
or CamelCase words?

*(I always use spaces in my multi-word tags because I find that easier to 
read.  And they wind up double-bracketed by TiddlyWiki in the tags fields.)*

On Tuesday, September 21, 2021 at 5:24:41 AM UTC-3 Eric Shulman wrote:

> On Monday, September 20, 2021 at 7:38:43 PM UTC-7 thor...@gmail.com wrote:
>
>> ...is there a shorthand to only output those tiddlers with _exactly_ the 
>> one tag I'm requesting
>>
>
> Even though the "tags" field contains a list of tiddler titles, it is also 
> just a simple text value and you can use the `fields:tags[...]` filter to 
> look for a specific literal value in the field, without it as a list.
>
> `<$list 
> filter="[field:tags[technical_todo]]"><>`
> will give the results you want, without a lot of messy "counting" and such.
>
> enjoy,
> -e
>
>

-- 
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/06a49bed-d604-4c86-94cb-6b341ec24558n%40googlegroups.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[Eric Shulman]

On Monday, September 20, 2021 at 7:38:43 PM UTC-7 thor...@gmail.com wrote:

> ...is there a shorthand to only output those tiddlers with _exactly_ the 
> one tag I'm requesting
>

Even though the "tags" field contains a list of tiddler titles, it is also 
just a simple text value and you can use the `fields:tags[...]` filter to 
look for a specific literal value in the field, without it as a list.

`<$list filter="[field:tags[technical_todo]]"><>
`
will give the results you want, without a lot of messy "counting" and such.

enjoy,
-e

-- 
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/dc1023c2-e1cd-469b-b29c-6b35ed92fd7cn%40googlegroups.com.

[tw5] Re: Filter tiddlers with exactly one tag.

[Charlie Veniot]

G'day,

Give the attached tiddler a spin.  (Download and then drag the file into 
TiddlyWiki.com.)





On Monday, September 20, 2021 at 11:38:43 PM UTC-3 thor...@gmail.com wrote:

> I wish to filter tiddlers with a `technical_todo` tag into "tiddlers which 
> I have already tagged with _another_ tag", and "tiddlers which have yet to 
> be tagged with further tags".
>
> A filter like `[tag[technical_todo]]` will return all tiddlers with the 
> tag `technical_todo`, regardless of whether these tiddlers have additional 
> tags. I can always futher filter out tags using more steps with 
> `[!tag[foo]]` (and this is of course useful too).
>
> But for the sake of organizing "otherwise-untagged" tiddlers, is there a 
> shorthand to only output those tiddlers with _exactly_ the one tag I'm 
> requesting? Perhaps by counting the number of tags each output tiddler from 
> `[tag[technical_todo]]` can get me those with only a single 
> `technical_todo` tag?
>

-- 
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/8551ea8f-2cb3-4769-a93a-c7935d85b70en%40googlegroups.com.


FilterExample.json
Description: application/json

Re: [tw5] Re: filter operator: sort by last part of title

[Mohammad Rahmani]

Saq,
Would you please have a look at
https://github.com/Jermolene/TiddlyWiki5/discussions/5941

It seems I cannot send the *reverse* flag as a variable for sort filter run
prefix!

Best wishes
Mohammad


On Fri, Aug 6, 2021 at 8:32 PM Saq Imtiaz  wrote:

>
> See this thread
>
> https://groups.google.com/g/tiddlywiki/c/ZXunGNpbG4c/m/ZIzuFq5iAQAJ
> On Friday, August 6, 2021 at 5:54:09 PM UTC+2 Mohammad wrote:
>
>> 1. goto https://tiddlywiki.com/prerelease/
>> 2. create three tiddlers with below titles all tagged with xtx as below
>> one: first
>> two: second
>> three: third
>>
>> 3. In another tiddler enter the below code
>>
>> \define myfilter() [split[:]last[]trim[]!sort[]]
>> <$list filter="[tag[xtx]filter]">
>>
>> 
>>
>> 4. The expected result is
>>
>> three: third
>> two: second
>> one: first
>>
>> BUT it does not work! What is wrong here?
>>
>>
>> Best wishes
>> Mohammad
>>
> --
> 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/055f2af6-da9b-4f11-a6e1-1d2ff5ee0ba5n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMBQ9b36BixwfJVmgs4uNyfZEfPKvjBOHTd9oXC2L0fXPA%40mail.gmail.com.

Re: [tw5] Re: filter operator: sort by last part of title

[Mohammad Rahmani]

Hi Saq,
 It is funny! With no doubt I have Alzheimer's! ;-)


Best wishes
Mohammad


On Fri, Aug 6, 2021 at 8:32 PM Saq Imtiaz  wrote:

>
> See this thread
>
> https://groups.google.com/g/tiddlywiki/c/ZXunGNpbG4c/m/ZIzuFq5iAQAJ
> On Friday, August 6, 2021 at 5:54:09 PM UTC+2 Mohammad wrote:
>
>> 1. goto https://tiddlywiki.com/prerelease/
>> 2. create three tiddlers with below titles all tagged with xtx as below
>> one: first
>> two: second
>> three: third
>>
>> 3. In another tiddler enter the below code
>>
>> \define myfilter() [split[:]last[]trim[]!sort[]]
>> <$list filter="[tag[xtx]filter]">
>>
>> 
>>
>> 4. The expected result is
>>
>> three: third
>> two: second
>> one: first
>>
>> BUT it does not work! What is wrong here?
>>
>>
>> Best wishes
>> Mohammad
>>
> --
> 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/055f2af6-da9b-4f11-a6e1-1d2ff5ee0ba5n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMDo3sX%3D1gZrPz6GYaKzxbWEQyhChpnFb1oZwZtHfvAbfg%40mail.gmail.com.

[tw5] Re: filter operator: sort by last part of title

[Saq Imtiaz]

See this thread

https://groups.google.com/g/tiddlywiki/c/ZXunGNpbG4c/m/ZIzuFq5iAQAJ
On Friday, August 6, 2021 at 5:54:09 PM UTC+2 Mohammad wrote:

> 1. goto https://tiddlywiki.com/prerelease/
> 2. create three tiddlers with below titles all tagged with xtx as below
> one: first
> two: second
> three: third
>
> 3. In another tiddler enter the below code
>
> \define myfilter() [split[:]last[]trim[]!sort[]]
> <$list filter="[tag[xtx]filter]">
>
> 
>
> 4. The expected result is
>
> three: third
> two: second
> one: first
>
> BUT it does not work! What is wrong here?
>
>
> Best wishes
> Mohammad
>

-- 
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/055f2af6-da9b-4f11-a6e1-1d2ff5ee0ba5n%40googlegroups.com.

[tw5] Re: filter question

[paulgilbert2000]

Thanks guys,
 
i don't mind the tag being replaced, i was more interested to know how to 
apply actions  to some but not all tiddlers listed, the button is there 
only to add the tag and  not to display the list, i just want the button  
to add the tag to only a subset of the list  that is tagged with example1

hope this makes sense

On Monday, July 26, 2021 at 9:13:14 AM UTC+2 TW Tones wrote:

> As fred points out  <$action-setfield tags="tag1"/> is to set the whole 
> tags field to tag1, obliterating any other contents.
>
> Since tags can hold more than one tagname or title you must treat it as a 
> list and use the actions designed for tags or use the listop actions. 
> Unless of course you want "obliteration" of the tags field.
>
> Regards
> Tones
>
> On Monday, 26 July 2021 at 11:55:21 UTC+10 fred@gmail.com wrote:
>
>> Hi Mohammad, can you expand a bit about the list you want to see? is this 
>> just when you click the button?
>> One issue is that the setfield will replace the example1 tag 
>> with tag1. Did you mean to show the list only after the change happened, or 
>> did you mean to *add *tag1 to the tiddlers that also have example1?
>> If you want to add a tag, you would be better off using the <$action-listops 
>> $tags="tag1"/> instead of <$action-setfield tags="tag1"/>
>> This will get you part way there...
>>
>> <$button>refresh list and add tag 1
>> 
>> <$action-listops $field="myfield" $filter="[[]]"/>
>> 
>> <$list filter="[tag[example1]] [tag[example2]] [tag[example3]]" 
>> variable="lister">
>> <$action-listops $field="myfield" $subfilter="[enlist]"/>
>> 
>> 
>> <$list filter="[tag[example1]]">
>> <$action-listops $tags="tag1"/>
>> 
>> 
>>
>> 
>> <$list filter="[list[!!myfield]]">
>>
>> 
>>
>>
>>
>> On Sunday, 25 July 2021 at 20:28:30 UTC-4 mohamed...@hotmail.com wrote:
>>
>>>
>>> Hi ,
>>>
>>> is it possible to assign an action to a button that would affect some 
>>> but not all tiddlers listed in a filter 
>>>
>>> so for example, i want to add "tag1" to all tiddlers tagged with 
>>> "example1"
>>>
>>> <$button> add tag 1
>>> <$list filter="[tag[example1]]" >
>>> <$action-setfield tags="tag1"/>
>>> 
>>> 
>>>
>>> but i also want to see all tiddlers tagged with  "example1", "example2" 
>>> and  "example3"..
>>>
>>> i can modify the filter to add all tiddlers tagged with "example1" , 
>>> "example2", "example3",  ... but then if i click the button the action will 
>>> affect all tiddlers , so is there way to set an action against some 
>>> tiddlers meeting a  certain criteria while keeping other tiddlers that 
>>> don't  not matching the criteria on display?
>>>
>>

-- 
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/da15f8ea-e3a3-43b0-b7ac-eac62828e707n%40googlegroups.com.

[tw5] Re: filter question

[TW Tones]

As fred points out  <$action-setfield tags="tag1"/> is to set the whole 
tags field to tag1, obliterating any other contents.

Since tags can hold more than one tagname or title you must treat it as a 
list and use the actions designed for tags or use the listop actions. 
Unless of course you want "obliteration" of the tags field.

Regards
Tones

On Monday, 26 July 2021 at 11:55:21 UTC+10 fred@gmail.com wrote:

> Hi Mohammad, can you expand a bit about the list you want to see? is this 
> just when you click the button?
> One issue is that the setfield will replace the example1 tag 
> with tag1. Did you mean to show the list only after the change happened, or 
> did you mean to *add *tag1 to the tiddlers that also have example1?
> If you want to add a tag, you would be better off using the <$action-listops 
> $tags="tag1"/> instead of <$action-setfield tags="tag1"/>
> This will get you part way there...
>
> <$button>refresh list and add tag 1
> 
> <$action-listops $field="myfield" $filter="[[]]"/>
> 
> <$list filter="[tag[example1]] [tag[example2]] [tag[example3]]" 
> variable="lister">
> <$action-listops $field="myfield" $subfilter="[enlist]"/>
> 
> 
> <$list filter="[tag[example1]]">
> <$action-listops $tags="tag1"/>
> 
> 
>
> 
> <$list filter="[list[!!myfield]]">
>
> 
>
>
>
> On Sunday, 25 July 2021 at 20:28:30 UTC-4 mohamed...@hotmail.com wrote:
>
>>
>> Hi ,
>>
>> is it possible to assign an action to a button that would affect some but 
>> not all tiddlers listed in a filter 
>>
>> so for example, i want to add "tag1" to all tiddlers tagged with 
>> "example1"
>>
>> <$button> add tag 1
>> <$list filter="[tag[example1]]" >
>> <$action-setfield tags="tag1"/>
>> 
>> 
>>
>> but i also want to see all tiddlers tagged with  "example1", "example2" 
>> and  "example3"..
>>
>> i can modify the filter to add all tiddlers tagged with "example1" , 
>> "example2", "example3",  ... but then if i click the button the action will 
>> affect all tiddlers , so is there way to set an action against some 
>> tiddlers meeting a  certain criteria while keeping other tiddlers that 
>> don't  not matching the criteria on display?
>>
>

-- 
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/61de3786-e880-4481-8d6f-ce98bff62344n%40googlegroups.com.

[tw5] Re: filter question

[Frédéric Demers]

Hi Mohammad, can you expand a bit about the list you want to see? is this 
just when you click the button?
One issue is that the setfield will replace the example1 tag with tag1. Did 
you mean to show the list only after the change happened, or did you mean 
to *add *tag1 to the tiddlers that also have example1?
If you want to add a tag, you would be better off using the <$action-listops 
$tags="tag1"/> instead of <$action-setfield tags="tag1"/>
This will get you part way there...

<$button>refresh list and add tag 1

<$action-listops $field="myfield" $filter="[[]]"/>

<$list filter="[tag[example1]] [tag[example2]] [tag[example3]]" 
variable="lister">
<$action-listops $field="myfield" $subfilter="[enlist]"/>


<$list filter="[tag[example1]]">
<$action-listops $tags="tag1"/>




<$list filter="[list[!!myfield]]">





On Sunday, 25 July 2021 at 20:28:30 UTC-4 mohamed...@hotmail.com wrote:

>
> Hi ,
>
> is it possible to assign an action to a button that would affect some but 
> not all tiddlers listed in a filter 
>
> so for example, i want to add "tag1" to all tiddlers tagged with "example1"
>
> <$button> add tag 1
> <$list filter="[tag[example1]]" >
> <$action-setfield tags="tag1"/>
> 
> 
>
> but i also want to see all tiddlers tagged with  "example1", "example2" 
> and  "example3"..
>
> i can modify the filter to add all tiddlers tagged with "example1" , 
> "example2", "example3",  ... but then if i click the button the action will 
> affect all tiddlers , so is there way to set an action against some 
> tiddlers meeting a  certain criteria while keeping other tiddlers that 
> don't  not matching the criteria on display?
>

-- 
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/37a5117e-8982-4c60-8020-75cd9bcc0406n%40googlegroups.com.

[tw5] Re: Filter a list with a variable that contains multiple words

[TW Tones]

Mat,

That is a good point, I will just add the alternative is to not use double 
quotes in any tiddler title, only use single quotes then "value" "filter" 
is sufficient.

Without going into the details now, we can use Unicode characters that look 
like quotes as well, but do not delimit like them eg “ 

Regards
Tones

On Thursday, 8 July 2021 at 23:54:33 UTC+10 Mat wrote:

> yeah, Eric is right. A small addition is that filters should generally be 
> enclosed in *triple* quotes because if any of the filtered out items has 
> quotes in it, then this can *conflict* with the enclosing filter quotes. 
> So, get into the habit of writing filter="""..."""
>
> To see the problem, you can test to create a new tiddler titled  This is 
> a "new" tiddler  and tag it with  About
>
> <:-)
> On Thursday, July 8, 2021 at 12:37:00 PM UTC+2 Eric Shulman wrote:
>
>> On Thursday, July 8, 2021 at 2:36:55 AM UTC-7 miket...@gmail.com wrote:
>>
>>> I'm trying to figure out how it works, simplified the example, and it 
>>> doesn't do anything. Does it not fit in newer versions?
>>> <$set name="myVar" filter='[tags[About]]'>
>>> <$list filter=''>
>>> 
>>>
>>
>> * The *[tags[]]* filter operator doesn't accept a operand value.  You 
>> want to use *[tag[About]]* to match tiddlers with the "About" tag.
>> * When using a *variable as a parameter value* (in the $list widget),  
>> do not enclose it in quotes, and use doubled angle brackets
>> * The $list widget needs some syntax inside it to indicate what to output
>>
>> Here's a corrected version of your example code:
>> <$set name="myVar" filter="[tag[About]]">
>> <$list filter=<>><$link/>
>> 
>>
>> -e
>>
>

-- 
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/c712c5de-3663-43a5-a9b6-dd531997cc83n%40googlegroups.com.

[tw5] Re: Filter to return tiddlers that do not contain any members of a given list

[Si]

Thank you very much Saq! (I assume you meant to put idListRegexp in curly 
braces?)

I have kind of a follow up question:

What if instead of using search terms as identifiers, I instead used 
filters. So for example I might have a tiddler with 
identifier:[search[my-example]] or identifier:[tag[Hello]].

Then I would want to return all tiddlers that don't satisfy *any* of the 
filters listed in an identifier field. Is there a way to do this?
On Saturday, 10 July 2021 at 16:11:09 UTC+1 saq.i...@gmail.com wrote:

> Assuming your identifiers are alphanumeric and do not contain characters 
> that might need to be escaped in regular expressions, something like this 
> should work:
>
> <$vars idListRegexp="[tag[Flashcard]get[identifier]join[|]]">
> <$list filter="[all[tiddlers]!regexp]">
> <>
> 
> 
>
> On Saturday, July 10, 2021 at 4:47:58 PM UTC+2 Si wrote:
>
>> Best explained with an example:
>>
>> I have a bunch of tiddlers tagged Flashcard, each with a field identifier 
>> containing some text.
>>
>> I want to return all the tiddlers that do not feature the values of *any* 
>> identifier fields within their text.
>>
>> Initially I tried the following:
>>
>> <$list filter="[tag[Flashcard]get[identifier]]" 
>> variable=flashcardIdentifier>
>> <$list filter="[!search]">
>> <>
>> 
>> 
>>
>> Of course this doesn't work because it is applying the search one at a 
>> time and is thus returning the tiddlers that don't contain *all* the 
>> identifiers. I want to return the tiddlers that don't contain *any* 
>> identifiers.
>>
>> Anyway now I'm stuck, so I'm wondering if anyone can help me out?
>>
>

-- 
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/4b742fae-9b7f-4919-adec-ccfd90f83016n%40googlegroups.com.

[tw5] Re: Filter to return tiddlers that do not contain any members of a given list

[Saq Imtiaz]

Assuming your identifiers are alphanumeric and do not contain characters 
that might need to be escaped in regular expressions, something like this 
should work:

<$vars idListRegexp="[tag[Flashcard]get[identifier]join[|]]">
<$list filter="[all[tiddlers]!regexp]">
<>



On Saturday, July 10, 2021 at 4:47:58 PM UTC+2 Si wrote:

> Best explained with an example:
>
> I have a bunch of tiddlers tagged Flashcard, each with a field identifier 
> containing 
> some text.
>
> I want to return all the tiddlers that do not feature the values of *any* 
> identifier fields within their text.
>
> Initially I tried the following:
>
> <$list filter="[tag[Flashcard]get[identifier]]" 
> variable=flashcardIdentifier>
> <$list filter="[!search]">
> <>
> 
> 
>
> Of course this doesn't work because it is applying the search one at a 
> time and is thus returning the tiddlers that don't contain *all* the 
> identifiers. I want to return the tiddlers that don't contain *any* 
> identifiers.
>
> Anyway now I'm stuck, so I'm wondering if anyone can help me out?
>

-- 
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/1c9be340-26c9-49c9-a8f7-17252000fb89n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

*This looks just what it needs! This is what I meant at the beginning.*

But for the sake of curiosity 邏 . I tried to do through the list. 

*filter="[tags[]prefix[$:/]]"*

Is it possible to make a variable in a list that will collect all the 
values?



*[all[]!is[system]] + '-[tag[*list result*]]'+ '-[tag[*list result*]]'+ 
'-[tag[*list result*]]'...*

And you get something like
<>  = [all[]!is[system]] -[tag[$:/tags/Stylesheet]] 
-[tag[$:/tags/PluginLibrary]] -[tag[$:/tags/Macro]] -[tag[$:/tags/Palette]]
And <$list filter=<>

-
Or in another way. I can do tiddler "*Sys Tag*" only with a filter

[all[]!is[system]] 
<$set name="myVar" filter="[tags[]prefix[$:/]]">
<$list filter=<>> -[tag[<$link/>]]


And one more with a button. Can I link to text from another post as a 
filter?

<$button>
  <$list filter=*{{Sys Tag}}* variable="tidToDelete">
<$action-deletetiddler $tiddler=<>/>
  
  DEL!


четверг, 8 июля 2021 г. в 13:22:52 UTC+3, Eric Shulman: 

> On Thursday, July 8, 2021 at 3:08:17 AM UTC-7 Eric Shulman wrote:
>
>> Then, you want to delete all tiddlers matching that filter.
>> You can do this directly using the filter tab in $:/AdvancedSearch.
>> Just enter the filter syntax as shown above and then press the delete 
>> button (trash can icon)
>>
>
> Addendum: You can also save the desired filter syntax and re-use it later:
> 1) Create a tiddler tagged with $:/tags/Filter
> 2) Add a field named "description" with a value of: *All Content Tiddlers*
> 3) Add a field named "filter" with a value of: *[all[]!is[system]] 
> -[tags[]prefix[$:/]tagging[]]*
> 4) Add a field named "list-before" with a blank field value
>
> Then, in the $:/AdvancedSearch filter tab, you can press the "down arrow" 
> next to the filter edit field to see
> a list of pre-defined filters and select "All Content Tiddlers" which will 
> appear as the first item in the list.
>
> -e
>

-- 
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/d4daf866-45f6-4afe-9585-0ec69ad9db2an%40googlegroups.com.

[tw5] Re: Filter a list with a variable that contains multiple words

[Mat]

yeah, Eric is right. A small addition is that filters should generally be 
enclosed in *triple* quotes because if any of the filtered out items has 
quotes in it, then this can *conflict* with the enclosing filter quotes. 
So, get into the habit of writing filter="""..."""

To see the problem, you can test to create a new tiddler titled  This is a 
"new" tiddler  and tag it with  About

<:-)
On Thursday, July 8, 2021 at 12:37:00 PM UTC+2 Eric Shulman wrote:

> On Thursday, July 8, 2021 at 2:36:55 AM UTC-7 miket...@gmail.com wrote:
>
>> I'm trying to figure out how it works, simplified the example, and it 
>> doesn't do anything. Does it not fit in newer versions?
>> <$set name="myVar" filter='[tags[About]]'>
>> <$list filter=''>
>> 
>>
>
> * The *[tags[]]* filter operator doesn't accept a operand value.  You 
> want to use *[tag[About]]* to match tiddlers with the "About" tag.
> * When using a *variable as a parameter value* (in the $list widget),  do 
> not enclose it in quotes, and use doubled angle brackets
> * The $list widget needs some syntax inside it to indicate what to output
>
> Here's a corrected version of your example code:
> <$set name="myVar" filter="[tag[About]]">
> <$list filter=<>><$link/>
> 
>
> -e
>

-- 
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/642ec5bf-d385-4395-937e-fca2c84fce46n%40googlegroups.com.

[tw5] Re: Filter a list with a variable that contains multiple words

[Eric Shulman]

On Thursday, July 8, 2021 at 2:36:55 AM UTC-7 miket...@gmail.com wrote:

> I'm trying to figure out how it works, simplified the example, and it 
> doesn't do anything. Does it not fit in newer versions?
> <$set name="myVar" filter='[tags[About]]'>
> <$list filter=''>
> 
>

* The *[tags[]]* filter operator doesn't accept a operand value.  You want 
to use *[tag[About]]* to match tiddlers with the "About" tag.
* When using a *variable as a parameter value* (in the $list widget),  do 
not enclose it in quotes, and use doubled angle brackets
* The $list widget needs some syntax inside it to indicate what to output

Here's a corrected version of your example code:
<$set name="myVar" filter="[tag[About]]">
<$list filter=<>><$link/>


-e

-- 
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/bf369de0-edec-45f7-8721-355f9a820edcn%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Eric Shulman]

On Thursday, July 8, 2021 at 3:08:17 AM UTC-7 Eric Shulman wrote:

> Then, you want to delete all tiddlers matching that filter.
> You can do this directly using the filter tab in $:/AdvancedSearch.
> Just enter the filter syntax as shown above and then press the delete 
> button (trash can icon)
>

Addendum: You can also save the desired filter syntax and re-use it later:
1) Create a tiddler tagged with $:/tags/Filter
2) Add a field named "description" with a value of: *All Content Tiddlers*
3) Add a field named "filter" with a value of: *[all[]!is[system]] 
-[tags[]prefix[$:/]tagging[]]*
4) Add a field named "list-before" with a blank field value

Then, in the $:/AdvancedSearch filter tab, you can press the "down arrow" 
next to the filter edit field to see
a list of pre-defined filters and select "All Content Tiddlers" which will 
appear as the first item in the list.

-e

-- 
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/86a6f7b1-c8b5-442e-a247-167fde7acfcfn%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Eric Shulman]

On Thursday, July 8, 2021 at 2:21:37 AM UTC-7 miket...@gmail.com wrote:

> I realized that the task is more difficult. It is necessary not only to 
> process it in a loop, but to form a new line with all the tags.
>

If I understand your goal, you want to *identify all tiddlers that are not 
system tiddlers, excluding those that have a tag that starts with $:/*
Here's the filter syntax that does that:

[all[]!is[system]] -[tags[]prefix[$:/]tagging[]]

Then, you want to delete all tiddlers matching that filter.
You can do this directly using the filter tab in $:/AdvancedSearch.
Just enter the filter syntax as shown above and then press the delete 
button (trash can icon)

You can also do this by defining a $button that triggers 
$action-deletetiddler using a $filter parameter rather than a $tiddler 
parameter, like this:
<$button> delete content
   <$action-deletetiddler $filter="[all[]!is[system]] 
-[tags[]prefix[$:/]tagging[]]" />


enjoy,
-e

-- 
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/db99eb2f-1772-431c-8f10-7f8c9792db57n%40googlegroups.com.

[tw5] Re: Filter a list with a variable that contains multiple words

[Mike Andyl]

I'm trying to figure out how it works, simplified the example, and it 
doesn't do anything. Does it not fit in newer versions?

<$set name="myVar" filter='[tags[About]]'>
<$list filter=''>


четверг, 17 ноября 2016 г. в 11:27:17 UTC+3, fidel...@gmail.com: 

> Any opportunity is good to learn about TW internals, thanks for the 
> explanation and the replacement code it was very useful to me, and allows 
> for the use of operators with multiple words. 
> Then again, shoudlnt that be in the main documentation of operators? So 
> people can use them with multi-word variables?
>
>
> On Wednesday, November 16, 2016 at 1:25:35 PM UTC+1, Jed Carty wrote:
>>
>> This is a very annoying property of the set widget that I am unhappy with 
>> that a lot of the operators added with action-listops also use. The problem 
>> is that the set widget returns each word as a separate list item and 
>> doesn't handle titles with spaces in a way that plays well with other 
>> things. I thought in this context the list widget fixed the problem but the 
>> remove operator has the same thing where it will only take a multi-word 
>> input as a single item if it has [[ and ]] around it. 
>>
>> One way to use the remove operator like you want is like this:
>>
>> <$set name="myVar" filter='[]'>
>> <$list filter='[is[current]tags[]remove]'>
>> 
>>
>> I will be quiet now since I think you have a solution and this is just be 
>> me complaining :p
>>
>

-- 
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/700d2f2f-1006-408a-a992-3a313754d7c9n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

I realized that the task is more difficult. It is necessary not only to 
process it in a loop, but to form a new line with all the tags.
Can TiddlyWiki work with strings? I have not found such examples anywhere.
In another language, I would do this:

t = "[all[]!is[system]]"
<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
t = t + " -[tag[" + <> + "]]" 


<$list filter= t variable="tidToDelete">
<$action-deletetiddler $tiddler=<>/>


среда, 7 июля 2021 г. в 16:59:31 UTC+3, Mike Andyl: 

> Ok, but I can skip and delete something I want anyway. Forget the 
> important tag in a year or two :)
>
> I have a list of tags *[tags[]prefix[$:/]]*
> Can I wrap it like a ? Make a button action so it can process in a 
> loop?
> <$action-deletetiddler...
>
> Something like this, but I'm confused about the variables again.
> Why isn't -[tag[<>]] working?
>
> <$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
>   <>
>   <$list filter="[all[]!is[system]] *-[tag[<>]]*" 
> variable="tidToDelete">
> <>
>   
> 
>
> среда, 7 июля 2021 г. в 15:23:16 UTC+3, TW Tones: 
>
>> miket,
>>
>> You can remove and add back
>>
>> [all[]!is[system]] [tag[$:/tags/MenuBar]] [tag[$:/tags/SideBar]]
>>
>> Thus above is all tiddlers except system, tiddlers adding back those 
>> tagged  $:/tags/MenuBaror  $:/tags/SideBar
>>
>> Tones
>>
>> On Wednesday, 7 July 2021 at 22:13:59 UTC+10 miket...@gmail.com wrote:
>>
>>> This is understandable, but it requires additional actions. I can forget 
>>> or miss something in a hurry, I cannot do it with someone else's databases 
>>> or an old database, and so on. It's just that we already have the NECESSARY 
>>> attribute - the beginning of the tag with "$:/".
>>>
>>> How can I subtract all such entries from *all[]!is[system]* ?
>>> It sounds very simple, can't filters really do that?
>>>
>>> среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 
>>>
 I think  you are somewhat doing this around the wrong way.

 Use a filter to list all your non-content tiddlers, eg the tiddler you 
 use in the side bar etc... macros etc...

- You may use a title prefix, tag or even a field with a value eg; 
project=setup then the filter [all[]project[setup]]

 Then you can have a filter that lists every tiddler 
 "[all[]!is[system]]" thing that is not in your above filter. eg; 
 "[all[]!is[system]!project[setup]]"
 Both sets of tiddlers can be exported separately and then imported into 
 an empty.html

 Regards
 Tones

 On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:

> I tried it doesn't fit. Since many records are not related to the 
> system. It is necessary to do on the tag, I think so. For example, new 
> buttons with the tag  *$:/tags/SideBar*. This is not a system entry 
> and it will disappear.
>
> вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 
>
>> [!is[system]] in the filter tab of Advanced search. But make sure you 
>> don't have any regular tiddlers that are needed for your template (base).
>>
>> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com 
>> wrote:
>>
>>> Let's say I set everything up and want to make a new base. I want to 
>>> remove only information posts, but keep all my own customizations, CSS 
>>> and 
>>> plugins.
>>> Post with similar tags:
>>> $:/tags/Stylesheet CSS 
>>> $:/tags/MenuBar
>>> $:/tags/SideBar
>>> ...
>>> etc
>>>
>>> Am I thinking right? Or is it possible to clear the base faster?
>>> And what filter is needed for this?
>>> [all[tiddlers]] - ??? prefix[$:/]
>>>
>>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>>
>>

-- 
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/56eee55d-e379-4ad6-9fcb-956b4200aff0n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

Ok, but I can skip and delete something I want anyway. Forget the important 
tag in a year or two :)

I have a list of tags *[tags[]prefix[$:/]]*
Can I wrap it like a ? Make a button action so it can process in a 
loop?
<$action-deletetiddler...

Something like this, but I'm confused about the variables again.
Why isn't -[tag[<>]] working?

<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
  <>
  <$list filter="[all[]!is[system]] *-[tag[<>]]*" 
variable="tidToDelete">
<>
  


среда, 7 июля 2021 г. в 15:23:16 UTC+3, TW Tones: 

> miket,
>
> You can remove and add back
>
> [all[]!is[system]] [tag[$:/tags/MenuBar]] [tag[$:/tags/SideBar]]
>
> Thus above is all tiddlers except system, tiddlers adding back those 
> tagged  $:/tags/MenuBaror  $:/tags/SideBar
>
> Tones
>
> On Wednesday, 7 July 2021 at 22:13:59 UTC+10 miket...@gmail.com wrote:
>
>> This is understandable, but it requires additional actions. I can forget 
>> or miss something in a hurry, I cannot do it with someone else's databases 
>> or an old database, and so on. It's just that we already have the NECESSARY 
>> attribute - the beginning of the tag with "$:/".
>>
>> How can I subtract all such entries from *all[]!is[system]* ?
>> It sounds very simple, can't filters really do that?
>>
>> среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 
>>
>>> I think  you are somewhat doing this around the wrong way.
>>>
>>> Use a filter to list all your non-content tiddlers, eg the tiddler you 
>>> use in the side bar etc... macros etc...
>>>
>>>- You may use a title prefix, tag or even a field with a value eg; 
>>>project=setup then the filter [all[]project[setup]]
>>>
>>> Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
>>> thing that is not in your above filter. eg; 
>>> "[all[]!is[system]!project[setup]]"
>>> Both sets of tiddlers can be exported separately and then imported into 
>>> an empty.html
>>>
>>> Regards
>>> Tones
>>>
>>> On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:
>>>
 I tried it doesn't fit. Since many records are not related to the 
 system. It is necessary to do on the tag, I think so. For example, new 
 buttons with the tag  *$:/tags/SideBar*. This is not a system entry 
 and it will disappear.

 вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 

> [!is[system]] in the filter tab of Advanced search. But make sure you 
> don't have any regular tiddlers that are needed for your template (base).
>
> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>
>> Let's say I set everything up and want to make a new base. I want to 
>> remove only information posts, but keep all my own customizations, CSS 
>> and 
>> plugins.
>> Post with similar tags:
>> $:/tags/Stylesheet CSS 
>> $:/tags/MenuBar
>> $:/tags/SideBar
>> ...
>> etc
>>
>> Am I thinking right? Or is it possible to clear the base faster?
>> And what filter is needed for this?
>> [all[tiddlers]] - ??? prefix[$:/]
>>
>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>
>

-- 
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/b83d2e19-fe21-4d03-9012-653499ec548fn%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

 Ok, but I can skip and delete something I want anyway. Forget the 
important tag in a year or two :)

I have a list of tags [tags[]prefix[$:/]]

Can I wrap it like a ? Make a button action so it can process in a 
loop?
<$action-deletetiddler...

Something like this, but I'm confused about the variables again.
Why isn't *-<>* working?

<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
  <>
  <$list filter="[all[]!is[system]] *-<>*" 
variable="tidToDelete">
<>
  


<$button>
<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
  <$list filter="[all[]!is[system]] *-<>*" 
variable="tidToDelete">
<$action-deletetiddler $tiddler=<>/>
  

 

среда, 7 июля 2021 г. в 15:23:16 UTC+3, TW Tones: 

> miket,
>
> You can remove and add back
>
> [all[]!is[system]] [tag[$:/tags/MenuBar]] [tag[$:/tags/SideBar]]
>
> Thus above is all tiddlers except system, tiddlers adding back those 
> tagged  $:/tags/MenuBaror  $:/tags/SideBar
>
> Tones
>
> On Wednesday, 7 July 2021 at 22:13:59 UTC+10 miket...@gmail.com wrote:
>
>> This is understandable, but it requires additional actions. I can forget 
>> or miss something in a hurry, I cannot do it with someone else's databases 
>> or an old database, and so on. It's just that we already have the NECESSARY 
>> attribute - the beginning of the tag with "$:/".
>>
>> How can I subtract all such entries from *all[]!is[system]* ?
>> It sounds very simple, can't filters really do that?
>>
>> среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 
>>
>>> I think  you are somewhat doing this around the wrong way.
>>>
>>> Use a filter to list all your non-content tiddlers, eg the tiddler you 
>>> use in the side bar etc... macros etc...
>>>
>>>- You may use a title prefix, tag or even a field with a value eg; 
>>>project=setup then the filter [all[]project[setup]]
>>>
>>> Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
>>> thing that is not in your above filter. eg; 
>>> "[all[]!is[system]!project[setup]]"
>>> Both sets of tiddlers can be exported separately and then imported into 
>>> an empty.html
>>>
>>> Regards
>>> Tones
>>>
>>> On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:
>>>
 I tried it doesn't fit. Since many records are not related to the 
 system. It is necessary to do on the tag, I think so. For example, new 
 buttons with the tag  *$:/tags/SideBar*. This is not a system entry 
 and it will disappear.

 вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 

> [!is[system]] in the filter tab of Advanced search. But make sure you 
> don't have any regular tiddlers that are needed for your template (base).
>
> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>
>> Let's say I set everything up and want to make a new base. I want to 
>> remove only information posts, but keep all my own customizations, CSS 
>> and 
>> plugins.
>> Post with similar tags:
>> $:/tags/Stylesheet CSS 
>> $:/tags/MenuBar
>> $:/tags/SideBar
>> ...
>> etc
>>
>> Am I thinking right? Or is it possible to clear the base faster?
>> And what filter is needed for this?
>> [all[tiddlers]] - ??? prefix[$:/]
>>
>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>
>

-- 
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/5e5a2000-ef1c-44fe-9dae-1c99dfaad4e4n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

Ok, but I can skip and delete something I want anyway. Forget the important 
tag in a year or two :)

I have a list of tags [tags[]prefix[$:/]]

Can I wrap it like a ? Make a button action so it can process in a 
loop?
<$action-deletetiddler...

Something like this, but I'm confused about the variables again.
Why isn't -<> working?

<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
  <>
  <$list filter="[all[]!is[system]] -<>" 
variable="tidToDelete">
<>
  


<$button>
<$list filter="[tags[]prefix[$:/]]" variable="TagToDelete">
  <$list filter="[all[]!is[system]] -<>" 
variable="tidToDelete">
<$action-deletetiddler $tiddler=<>/>
  



среда, 7 июля 2021 г. в 15:23:16 UTC+3, TW Tones: 

> miket,
>
> You can remove and add back
>
> [all[]!is[system]] [tag[$:/tags/MenuBar]] [tag[$:/tags/SideBar]]
>
> Thus above is all tiddlers except system, tiddlers adding back those 
> tagged  $:/tags/MenuBaror  $:/tags/SideBar
>
> Tones
>
> On Wednesday, 7 July 2021 at 22:13:59 UTC+10 miket...@gmail.com wrote:
>
>> This is understandable, but it requires additional actions. I can forget 
>> or miss something in a hurry, I cannot do it with someone else's databases 
>> or an old database, and so on. It's just that we already have the NECESSARY 
>> attribute - the beginning of the tag with "$:/".
>>
>> How can I subtract all such entries from *all[]!is[system]* ?
>> It sounds very simple, can't filters really do that?
>>
>> среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 
>>
>>> I think  you are somewhat doing this around the wrong way.
>>>
>>> Use a filter to list all your non-content tiddlers, eg the tiddler you 
>>> use in the side bar etc... macros etc...
>>>
>>>- You may use a title prefix, tag or even a field with a value eg; 
>>>project=setup then the filter [all[]project[setup]]
>>>
>>> Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
>>> thing that is not in your above filter. eg; 
>>> "[all[]!is[system]!project[setup]]"
>>> Both sets of tiddlers can be exported separately and then imported into 
>>> an empty.html
>>>
>>> Regards
>>> Tones
>>>
>>> On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:
>>>
 I tried it doesn't fit. Since many records are not related to the 
 system. It is necessary to do on the tag, I think so. For example, new 
 buttons with the tag  *$:/tags/SideBar*. This is not a system entry 
 and it will disappear.

 вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 

> [!is[system]] in the filter tab of Advanced search. But make sure you 
> don't have any regular tiddlers that are needed for your template (base).
>
> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>
>> Let's say I set everything up and want to make a new base. I want to 
>> remove only information posts, but keep all my own customizations, CSS 
>> and 
>> plugins.
>> Post with similar tags:
>> $:/tags/Stylesheet CSS 
>> $:/tags/MenuBar
>> $:/tags/SideBar
>> ...
>> etc
>>
>> Am I thinking right? Or is it possible to clear the base faster?
>> And what filter is needed for this?
>> [all[tiddlers]] - ??? prefix[$:/]
>>
>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>
>

-- 
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/0a730777-24f2-4f96-8322-d220487828ddn%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[TW Tones]

miket,

You can remove and add back

[all[]!is[system]] [tag[$:/tags/MenuBar]] [tag[$:/tags/SideBar]]

Thus above is all tiddlers except system, tiddlers adding back those 
tagged  $:/tags/MenuBaror  $:/tags/SideBar

Tones

On Wednesday, 7 July 2021 at 22:13:59 UTC+10 miket...@gmail.com wrote:

> This is understandable, but it requires additional actions. I can forget 
> or miss something in a hurry, I cannot do it with someone else's databases 
> or an old database, and so on. It's just that we already have the NECESSARY 
> attribute - the beginning of the tag with "$:/".
>
> How can I subtract all such entries from *all[]!is[system]* ?
> It sounds very simple, can't filters really do that?
>
> среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 
>
>> I think  you are somewhat doing this around the wrong way.
>>
>> Use a filter to list all your non-content tiddlers, eg the tiddler you 
>> use in the side bar etc... macros etc...
>>
>>- You may use a title prefix, tag or even a field with a value eg; 
>>project=setup then the filter [all[]project[setup]]
>>
>> Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
>> thing that is not in your above filter. eg; 
>> "[all[]!is[system]!project[setup]]"
>> Both sets of tiddlers can be exported separately and then imported into 
>> an empty.html
>>
>> Regards
>> Tones
>>
>> On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:
>>
>>> I tried it doesn't fit. Since many records are not related to the 
>>> system. It is necessary to do on the tag, I think so. For example, new 
>>> buttons with the tag  *$:/tags/SideBar*. This is not a system entry and 
>>> it will disappear.
>>>
>>> вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 
>>>
 [!is[system]] in the filter tab of Advanced search. But make sure you 
 don't have any regular tiddlers that are needed for your template (base).

 On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:

> Let's say I set everything up and want to make a new base. I want to 
> remove only information posts, but keep all my own customizations, CSS 
> and 
> plugins.
> Post with similar tags:
> $:/tags/Stylesheet CSS 
> $:/tags/MenuBar
> $:/tags/SideBar
> ...
> etc
>
> Am I thinking right? Or is it possible to clear the base faster?
> And what filter is needed for this?
> [all[tiddlers]] - ??? prefix[$:/]
>
> I want to delete all my content posts, but not touch the "$:/*" tags.
>


-- 
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/4dd44ad6-2332-4c24-84e3-00e69699cf2fn%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

This is understandable, but it requires additional actions. I can forget or 
miss something in a hurry, I cannot do it with someone else's databases or 
an old database, and so on. It's just that we already have the NECESSARY 
attribute - the beginning of the tag with "$:/".

How can I subtract all such entries from *all[]!is[system]* ?
It sounds very simple, can't filters really do that?

среда, 7 июля 2021 г. в 11:31:29 UTC+3, TW Tones: 

> I think  you are somewhat doing this around the wrong way.
>
> Use a filter to list all your non-content tiddlers, eg the tiddler you use 
> in the side bar etc... macros etc...
>
>- You may use a title prefix, tag or even a field with a value eg; 
>project=setup then the filter [all[]project[setup]]
>
> Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
> thing that is not in your above filter. eg; 
> "[all[]!is[system]!project[setup]]"
> Both sets of tiddlers can be exported separately and then imported into an 
> empty.html
>
> Regards
> Tones
>
> On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:
>
>> I tried it doesn't fit. Since many records are not related to the system. 
>> It is necessary to do on the tag, I think so. For example, new buttons with 
>> the tag  *$:/tags/SideBar*. This is not a system entry and it will 
>> disappear.
>>
>> вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 
>>
>>> [!is[system]] in the filter tab of Advanced search. But make sure you 
>>> don't have any regular tiddlers that are needed for your template (base).
>>>
>>> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>>>
 Let's say I set everything up and want to make a new base. I want to 
 remove only information posts, but keep all my own customizations, CSS and 
 plugins.
 Post with similar tags:
 $:/tags/Stylesheet CSS 
 $:/tags/MenuBar
 $:/tags/SideBar
 ...
 etc

 Am I thinking right? Or is it possible to clear the base faster?
 And what filter is needed for this?
 [all[tiddlers]] - ??? prefix[$:/]

 I want to delete all my content posts, but not touch the "$:/*" tags.

>>>

-- 
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/bcacadda-f7bf-4145-8df7-b7ff9cbcc4c8n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[TW Tones]

I think  you are somewhat doing this around the wrong way.

Use a filter to list all your non-content tiddlers, eg the tiddler you use 
in the side bar etc... macros etc...

   - You may use a title prefix, tag or even a field with a value eg; 
   project=setup then the filter [all[]project[setup]]

Then you can have a filter that lists every tiddler "[all[]!is[system]]" 
thing that is not in your above filter. eg; 
"[all[]!is[system]!project[setup]]"
Both sets of tiddlers can be exported separately and then imported into an 
empty.html

Regards
Tones

On Tuesday, 6 July 2021 at 23:58:24 UTC+10 miket...@gmail.com wrote:

> I tried it doesn't fit. Since many records are not related to the system. 
> It is necessary to do on the tag, I think so. For example, new buttons with 
> the tag  *$:/tags/SideBar*. This is not a system entry and it will 
> disappear.
>
> вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 
>
>> [!is[system]] in the filter tab of Advanced search. But make sure you 
>> don't have any regular tiddlers that are needed for your template (base).
>>
>> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>>
>>> Let's say I set everything up and want to make a new base. I want to 
>>> remove only information posts, but keep all my own customizations, CSS and 
>>> plugins.
>>> Post with similar tags:
>>> $:/tags/Stylesheet CSS 
>>> $:/tags/MenuBar
>>> $:/tags/SideBar
>>> ...
>>> etc
>>>
>>> Am I thinking right? Or is it possible to clear the base faster?
>>> And what filter is needed for this?
>>> [all[tiddlers]] - ??? prefix[$:/]
>>>
>>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>>
>>

-- 
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/7746918f-8cc0-4725-8af7-3a2eacfc4910n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[Mike Andyl]

I tried it doesn't fit. Since many records are not related to the system. 
It is necessary to do on the tag, I think so. For example, new buttons with 
the tag  *$:/tags/SideBar*. This is not a system entry and it will 
disappear.

вторник, 6 июля 2021 г. в 16:26:36 UTC+3, David Gifford: 

> [!is[system]] in the filter tab of Advanced search. But make sure you 
> don't have any regular tiddlers that are needed for your template (base).
>
> On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:
>
>> Let's say I set everything up and want to make a new base. I want to 
>> remove only information posts, but keep all my own customizations, CSS and 
>> plugins.
>> Post with similar tags:
>> $:/tags/Stylesheet CSS 
>> $:/tags/MenuBar
>> $:/tags/SideBar
>> ...
>> etc
>>
>> Am I thinking right? Or is it possible to clear the base faster?
>> And what filter is needed for this?
>> [all[tiddlers]] - ??? prefix[$:/]
>>
>> I want to delete all my content posts, but not touch the "$:/*" tags.
>>
>

-- 
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/51929c3f-56c5-42e3-beb1-e3654afe7a12n%40googlegroups.com.

[tw5] Re: Filter for cleaning the base, but keeping the basic settings.

[David Gifford]

[!is[system]] in the filter tab of Advanced search. But make sure you don't 
have any regular tiddlers that are needed for your template (base).

On Tuesday, July 6, 2021 at 5:58:04 AM UTC-5 miket...@gmail.com wrote:

> Let's say I set everything up and want to make a new base. I want to 
> remove only information posts, but keep all my own customizations, CSS and 
> plugins.
> Post with similar tags:
> $:/tags/Stylesheet CSS 
> $:/tags/MenuBar
> $:/tags/SideBar
> ...
> etc
>
> Am I thinking right? Or is it possible to clear the base faster?
> And what filter is needed for this?
> [all[tiddlers]] - ??? prefix[$:/]
>
> I want to delete all my content posts, but not touch the "$:/*" tags.
>

-- 
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/a9c6bbd7-29e8-4faf-99ba-db8aa36184d0n%40googlegroups.com.

Re: [tw5] Re: Filter question: how to convert current tiddler title into a title list format

[Joshua Fontany]

Hi mehequeda,

You will want to read up on the 
"ListOps": https://tiddlywiki.com/#ActionListopsWidget

Best,
Joshua Fontany

On Tuesday, June 22, 2021 at 10:49:45 PM UTC-7 mehequeda...@gmail.com wrote:

> Thanks Saq, Tones and Jeremy, it was hidden in plain sight.
>
> The reason I need this is a design decision of some zettlekasten-like 
> features I'm implementing in my wiki. For example, tiddlers tagged with 
> Source are the books, articles, or other sources of concepts I want to 
> track and I've modified the view template to show some fields and 
> references to related things in a footer:
> [image: image.png]
> Now, I'm introducing buttons to create related tiddlers that have the kind 
> of relationship of the corresponding tab. Sometimes that means copying 
> current title in the author field. But in some case I need to set current 
> title in title list format because of the meaning of the field. For 
> example, a concept might have two authors.
>
> BTW, this is pretty much inspired by the amazing Soren's zettlekasten. 
> Thanks Soren!
>
> --
> Sebastián
>
>
> On Wed, Jun 23, 2021 at 2:20 AM TW Tones  wrote:
>
>> mehequeda,
>>
>> I am curious why you need to do this. Since titles are the key to all 
>> tiddler there handling as titles is innate to TiddlyWiki and the need to 
>> generate a title with the delimiters [[ and ]] is rare. An example would be 
>> using the listops functions and operators where this is handled 
>> automatically. Tiddlywiki finds or adds delimiters automatically in many 
>> cases for title handling, consider  else{!!title} used in a filter, the 
>> output will not split a tiddler title containing spaces into separate words.
>>
>> Regrads
>> Tones
>>
>> On Wednesday, 23 June 2021 at 07:10:04 UTC+10 mehequeda...@gmail.com 
>> wrote:
>>
>>> Hello wise tiddlywiki users,
>>>
>>> Let's say I want to convert the current tiddler title into list format. 
>>> For example:
>>>
>>>- For a tiddler named CamelCased, this is either CamelCased or 
>>>[[CamelCased]] (I prefer the format but I can settle with the latter)
>>>- For a tiddler named Name with spaces it must be [[Name with 
>>>spaces]]
>>>
>>> I'm stuck with trying to add squared brackets conditionally 
>>> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because 
>>> that's not the right syntax for adding the brackets and also because this 
>>> feels common enough that it should be some easier way to "escape" a string 
>>> to a title list format.
>>>
>>> Do you know how to get it?
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/S5LM0L5ZVRo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/e971bff9-cdf0-407a-bc6b-e8b47580c36an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/36b67124-16aa-49ba-9da1-80e99e863a2an%40googlegroups.com.

Re: [tw5] Re: Filter question: how to convert current tiddler title into a title list format

[Sebastián Ortega]

Thanks Saq, Tones and Jeremy, it was hidden in plain sight.

The reason I need this is a design decision of some zettlekasten-like
features I'm implementing in my wiki. For example, tiddlers tagged with
Source are the books, articles, or other sources of concepts I want to
track and I've modified the view template to show some fields and
references to related things in a footer:
[image: image.png]
Now, I'm introducing buttons to create related tiddlers that have the kind
of relationship of the corresponding tab. Sometimes that means copying
current title in the author field. But in some case I need to set current
title in title list format because of the meaning of the field. For
example, a concept might have two authors.

BTW, this is pretty much inspired by the amazing Soren's zettlekasten.
Thanks Soren!

--
Sebastián


On Wed, Jun 23, 2021 at 2:20 AM TW Tones  wrote:

> mehequeda,
>
> I am curious why you need to do this. Since titles are the key to all
> tiddler there handling as titles is innate to TiddlyWiki and the need to
> generate a title with the delimiters [[ and ]] is rare. An example would be
> using the listops functions and operators where this is handled
> automatically. Tiddlywiki finds or adds delimiters automatically in many
> cases for title handling, consider  else{!!title} used in a filter, the
> output will not split a tiddler title containing spaces into separate words.
>
> Regrads
> Tones
>
> On Wednesday, 23 June 2021 at 07:10:04 UTC+10 mehequeda...@gmail.com
> wrote:
>
>> Hello wise tiddlywiki users,
>>
>> Let's say I want to convert the current tiddler title into list format.
>> For example:
>>
>>- For a tiddler named CamelCased, this is either CamelCased or
>>[[CamelCased]] (I prefer the format but I can settle with the latter)
>>- For a tiddler named Name with spaces it must be [[Name with spaces]]
>>
>> I'm stuck with trying to add squared brackets conditionally
>> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because
>> that's not the right syntax for adding the brackets and also because this
>> feels common enough that it should be some easier way to "escape" a string
>> to a title list format.
>>
>> Do you know how to get it?
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/S5LM0L5ZVRo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/e971bff9-cdf0-407a-bc6b-e8b47580c36an%40googlegroups.com
> 
> .
>

-- 
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/CAH9hHPj4WP%3DmMY%3D486daDfy76RfKkRiufqrTvbcUZh1_yE51gg%40mail.gmail.com.

[tw5] Re: Filter question: how to convert current tiddler title into a title list format

[TW Tones]

mehequeda,

I am curious why you need to do this. Since titles are the key to all 
tiddler there handling as titles is innate to TiddlyWiki and the need to 
generate a title with the delimiters [[ and ]] is rare. An example would be 
using the listops functions and operators where this is handled 
automatically. Tiddlywiki finds or adds delimiters automatically in many 
cases for title handling, consider  else{!!title} used in a filter, the 
output will not split a tiddler title containing spaces into separate words.

Regrads
Tones

On Wednesday, 23 June 2021 at 07:10:04 UTC+10 mehequeda...@gmail.com wrote:

> Hello wise tiddlywiki users,
>
> Let's say I want to convert the current tiddler title into list format. 
> For example:
>
>- For a tiddler named CamelCased, this is either CamelCased or 
>[[CamelCased]] (I prefer the format but I can settle with the latter)
>- For a tiddler named Name with spaces it must be [[Name with spaces]]
>
> I'm stuck with trying to add squared brackets conditionally 
> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because 
> that's not the right syntax for adding the brackets and also because this 
> feels common enough that it should be some easier way to "escape" a string 
> to a title list format.
>
> Do you know how to get it?
>
>

-- 
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/e971bff9-cdf0-407a-bc6b-e8b47580c36an%40googlegroups.com.

[tw5] Re: Filter question: how to convert current tiddler title into a title list format

[PMario]

Hi, 
See: https://tiddlywiki.com/#SetWidget   Especially the section: Filter 
List Variable Assignment
-mario


-- 
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/955e216d-ccc7-48b9-a438-aa883ac9d1d6n%40googlegroups.com.

[tw5] Re: Filter question: how to convert current tiddler title into a title list format

[Saq Imtiaz]

For now that is the best we have.

However from the next TW release we can use format:titlelist[]
https://tiddlywiki.com/prerelease/#format%20Operator
On Tuesday, June 22, 2021 at 11:18:55 PM UTC+2 mehequeda...@gmail.com wrote:

> I managed to fix the filter but I still feel there must be an easier way 
> to do it.
>
> <$vars prefix="[[" suffix="]]">
> <$button>
> <$action-sendmessage
> $message="tm-new-tiddler"
> source={{{ 
> [all[current]regexp[\s]addprefixaddsuffixelse{!!title}] }}}
> author={{!!author}}/>
> Add
> 
> 
>
> On Tuesday, 22 June 2021 at 23:10:04 UTC+2 Sebastián Ortega wrote:
>
>> Hello wise tiddlywiki users,
>>
>> Let's say I want to convert the current tiddler title into list format. 
>> For example:
>>
>>- For a tiddler named CamelCased, this is either CamelCased or 
>>[[CamelCased]] (I prefer the format but I can settle with the latter)
>>- For a tiddler named Name with spaces it must be [[Name with spaces]]
>>
>> I'm stuck with trying to add squared brackets conditionally 
>> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because 
>> that's not the right syntax for adding the brackets and also because this 
>> feels common enough that it should be some easier way to "escape" a string 
>> to a title list format.
>>
>> Do you know how to get it?
>>
>>

-- 
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/ad14ef20-d1da-4b55-aaac-17407cf240d1n%40googlegroups.com.

[tw5] Re: Filter question: how to convert current tiddler title into a title list format

[Sebastián Ortega]

I managed to fix the filter but I still feel there must be an easier way to 
do it.

<$vars prefix="[[" suffix="]]">
<$button>
<$action-sendmessage
$message="tm-new-tiddler"
source={{{ 
[all[current]regexp[\s]addprefixaddsuffixelse{!!title}] }}}
author={{!!author}}/>
Add



On Tuesday, 22 June 2021 at 23:10:04 UTC+2 Sebastián Ortega wrote:

> Hello wise tiddlywiki users,
>
> Let's say I want to convert the current tiddler title into list format. 
> For example:
>
>- For a tiddler named CamelCased, this is either CamelCased or 
>[[CamelCased]] (I prefer the format but I can settle with the latter)
>- For a tiddler named Name with spaces it must be [[Name with spaces]]
>
> I'm stuck with trying to add squared brackets conditionally 
> [all[current]regexp[\s]addprefix[[[]addsuffix[]]]else{!!title}] because 
> that's not the right syntax for adding the brackets and also because this 
> feels common enough that it should be some easier way to "escape" a string 
> to a title list format.
>
> Do you know how to get it?
>
>

-- 
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/e56858cc-32ea-4204-b571-9c31e796cc7en%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[TW Tones]

Folks,

The solution is in this thread, however there is value dividing the problem.

First construct a custom filter to extract and list transclusions within 
the current tiddler eg has {{ }} brackets, you can split on | (use \define 
pipe() | ) and get the last value (not }}). 

Once you have this list you can use it to exclude those tiddlers from the 
larger list.

Regards
Tones

On Friday, 18 June 2021 at 20:28:08 UTC+10 Si wrote:

> @Soren Yes I too would love to see this added, it would be very handy.
> On Wednesday, 16 June 2021 at 23:09:12 UTC+1 Soren Bjornstad wrote:
>
>> I'd like to draw attention to this PR that's been sitting for about a 
>> year due to needed improvements:
>> https://github.com/Jermolene/TiddlyWiki5/pull/4766
>>
>> By making transclusion into a first-class citizen that TiddlyWiki keeps 
>> track of, it would produce an elegant solution for this problem and many 
>> others. 
>>
>> On Wednesday, June 16, 2021 at 11:20:37 AM UTC-5 David Gifford wrote:
>>
>>> I added this to my "documenting.tw" file:  
>>> https://giffmex.org/gifts/documenting.tw.html#Filter%3A%20All%20tagging%20except%20those%20transcluded%20here
>>>
>>> On Wednesday, June 16, 2021 at 9:27:16 AM UTC-5 Si wrote:
>>>
 Hi David,

 I've been planning to do something similar in my own wiki. I can't 
 think of a way to do it with a single filter expression, but here is a 
 very 
 clunky approach:

 <$list filter="[tag] [tag{!!draft.of}]" 
 variable=tagged-tiddler>
 <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
 }}}>
 <$list filter="[!search]">
 <$link to=<>><>
 
 
 
 

 This should work in both edit and view mode, but you can easily 
 simplify the first filter expression if you only need it to work in edit 
 mode.

 There's probably a more elegant approach out there but this seems to 
 work.

 On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:

> Hi all
>
> I need another list filter:
>
> ...minus any tiddlers transcluded in the" current tiddler.
>
> Use case: I plan to use transclusions to build long "article" 
> tiddlers, with section headers and specific ordering of the 
> transclusions. 
> But as I take notes, I want to tag note tiddlers with the article(s) they 
> will be transcluded in. 
>
> So in edit template, I want a list at the bottom of the tiddlers 
> tagged to the current tiddler [all[current]tagging[]], minus the tiddlers 
> I 
> have already transcluded in the current tiddler. That way I can see which 
> tiddlers still need transcluding.
>
> Thanks for any help with this. It doesn't look very straightforward. 
> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
> Maybe in 5.1.25?
>
> Blessings,
>


-- 
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/40b46b67-11fd-494d-96d7-bc2556bf9c9bn%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Si]

@Soren Yes I too would love to see this added, it would be very handy.
On Wednesday, 16 June 2021 at 23:09:12 UTC+1 Soren Bjornstad wrote:

> I'd like to draw attention to this PR that's been sitting for about a year 
> due to needed improvements:
> https://github.com/Jermolene/TiddlyWiki5/pull/4766
>
> By making transclusion into a first-class citizen that TiddlyWiki keeps 
> track of, it would produce an elegant solution for this problem and many 
> others. 
>
> On Wednesday, June 16, 2021 at 11:20:37 AM UTC-5 David Gifford wrote:
>
>> I added this to my "documenting.tw" file:  
>> https://giffmex.org/gifts/documenting.tw.html#Filter%3A%20All%20tagging%20except%20those%20transcluded%20here
>>
>> On Wednesday, June 16, 2021 at 9:27:16 AM UTC-5 Si wrote:
>>
>>> Hi David,
>>>
>>> I've been planning to do something similar in my own wiki. I can't think 
>>> of a way to do it with a single filter expression, but here is a very 
>>> clunky approach:
>>>
>>> <$list filter="[tag] [tag{!!draft.of}]" 
>>> variable=tagged-tiddler>
>>> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
>>> }}}>
>>> <$list filter="[!search]">
>>> <$link to=<>><>
>>> 
>>> 
>>> 
>>> 
>>>
>>> This should work in both edit and view mode, but you can easily simplify 
>>> the first filter expression if you only need it to work in edit mode.
>>>
>>> There's probably a more elegant approach out there but this seems to 
>>> work.
>>>
>>> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>>>
 Hi all

 I need another list filter:

 ...minus any tiddlers transcluded in the" current tiddler.

 Use case: I plan to use transclusions to build long "article" tiddlers, 
 with section headers and specific ordering of the transclusions. But as I 
 take notes, I want to tag note tiddlers with the article(s) they will be 
 transcluded in. 

 So in edit template, I want a list at the bottom of the tiddlers tagged 
 to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
 already transcluded in the current tiddler. That way I can see which 
 tiddlers still need transcluding.

 Thanks for any help with this. It doesn't look very straightforward. 
 There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
 Maybe in 5.1.25?

 Blessings,

>>>

-- 
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/507067dc-6e41-4163-a91c-8422dc3482a6n%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[PMario]

On Thursday, June 17, 2021 at 1:45:51 AM UTC+2 TW Tones wrote:

as far as I can see I can replicate you filter with [tag[Widgets]sort[]] 
> +[get[caption]else[{!!title}]] while neither this or your filter provides 
> links to the original tiddler.
>

That doesn't produce the same results. Your filter returns 48 elements and 
Saqs filter returns 52. 

[tag[Widgets]] also returns 52 elements.

+[get[caption]else[{!!title}]] ... doesn't work the way as it seems. It 
doesn't use the title of the input it uses the title of the tiddler where 
the filter is used. 

reduce has some special "internal" variables. See: 
https://tiddlywiki.com/prerelease/#reduce%20Operator

-mario.

-- 
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/aebe945a-46cf-4398-b470-70ef67286bb0n%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Saq,

Well then either I don't understand what you are saying and/or you don't 
understand what I am saying (or both).

as far as I can see I can replicate you filter with [tag[Widgets]sort[]] 
+[get[caption]else[{!!title}]] while neither this or your filter provides 
links to the original tiddler.

Your question was how to get a similar result to your filter that you give 
an example for?, but you do not specifically state what result you are 
looking for. As a Result I speculated and came to think you want an 
intermediate result while retaining the currentTiddler. I then go on to 
talk about how this may be achieved in the future, in a simplified form of 
your filter which while an impressive use of the new filters it is hardly 
readable for most.

Perhaps I have not answered your question, but I did my best and put in 
some though and effort. Always with a view to improving tiddlywiki.

Regards
Tones



On Wednesday, 16 June 2021 at 17:03:14 UTC+10 Saq Imtiaz wrote:

> @pmario thank you for taking a look. Oddly enough, this came up now as I 
> was trying to see if I could replace a custom filter with the new filter 
> capabilities in the core.
>
> There are actually multiple ways that we could address this with a new 
> filter but I haven't had the chance to think through them and figure out 
> which would have the most universal utility. I'll post something on Github 
> when I get the chance. 
>
> Thank you.
>
>
> On Wednesday, June 16, 2021 at 8:39:24 AM UTC+2 PMario wrote:
>
>> Hi Saq,
>> That's a tricky filter. You use the capability of the "reduce" filter, 
>> that it has access to the "currentTiddler" inside the filter run. 
>>
>> If "elseXX" would have the same info it would be as simple as this. 
>>
>> [tag[Widgets]] +[get[caption]elseXX{!!title}]
>>
>> I think, the usecase is "generic" enough, to discuss a new elseX 
>> operator, that has this info.
>>
>> Just a thought
>> -mario
>>
>

-- 
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/e8aeaa32-cd59-4e10-a83c-cfcc1b57687bn%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Soren Bjornstad]

I'd like to draw attention to this PR that's been sitting for about a year 
due to needed improvements:
https://github.com/Jermolene/TiddlyWiki5/pull/4766

By making transclusion into a first-class citizen that TiddlyWiki keeps 
track of, it would produce an elegant solution for this problem and many 
others. 

On Wednesday, June 16, 2021 at 11:20:37 AM UTC-5 David Gifford wrote:

> I added this to my "documenting.tw" file:  
> https://giffmex.org/gifts/documenting.tw.html#Filter%3A%20All%20tagging%20except%20those%20transcluded%20here
>
> On Wednesday, June 16, 2021 at 9:27:16 AM UTC-5 Si wrote:
>
>> Hi David,
>>
>> I've been planning to do something similar in my own wiki. I can't think 
>> of a way to do it with a single filter expression, but here is a very 
>> clunky approach:
>>
>> <$list filter="[tag] [tag{!!draft.of}]" 
>> variable=tagged-tiddler>
>> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
>> }}}>
>> <$list filter="[!search]">
>> <$link to=<>><>
>> 
>> 
>> 
>> 
>>
>> This should work in both edit and view mode, but you can easily simplify 
>> the first filter expression if you only need it to work in edit mode.
>>
>> There's probably a more elegant approach out there but this seems to work.
>>
>> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>>
>>> Hi all
>>>
>>> I need another list filter:
>>>
>>> ...minus any tiddlers transcluded in the" current tiddler.
>>>
>>> Use case: I plan to use transclusions to build long "article" tiddlers, 
>>> with section headers and specific ordering of the transclusions. But as I 
>>> take notes, I want to tag note tiddlers with the article(s) they will be 
>>> transcluded in. 
>>>
>>> So in edit template, I want a list at the bottom of the tiddlers tagged 
>>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
>>> already transcluded in the current tiddler. That way I can see which 
>>> tiddlers still need transcluding.
>>>
>>> Thanks for any help with this. It doesn't look very straightforward. 
>>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
>>> Maybe in 5.1.25?
>>>
>>> Blessings,
>>>
>>

-- 
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/8ca8ae51-49c6-4674-8a2b-0cd11e6bee0fn%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[David Gifford]

I added this to my "documenting.tw" file:  
https://giffmex.org/gifts/documenting.tw.html#Filter%3A%20All%20tagging%20except%20those%20transcluded%20here

On Wednesday, June 16, 2021 at 9:27:16 AM UTC-5 Si wrote:

> Hi David,
>
> I've been planning to do something similar in my own wiki. I can't think 
> of a way to do it with a single filter expression, but here is a very 
> clunky approach:
>
> <$list filter="[tag] [tag{!!draft.of}]" 
> variable=tagged-tiddler>
> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
> }}}>
> <$list filter="[!search]">
> <$link to=<>><>
> 
> 
> 
> 
>
> This should work in both edit and view mode, but you can easily simplify 
> the first filter expression if you only need it to work in edit mode.
>
> There's probably a more elegant approach out there but this seems to work.
>
> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>
>> Hi all
>>
>> I need another list filter:
>>
>> ...minus any tiddlers transcluded in the" current tiddler.
>>
>> Use case: I plan to use transclusions to build long "article" tiddlers, 
>> with section headers and specific ordering of the transclusions. But as I 
>> take notes, I want to tag note tiddlers with the article(s) they will be 
>> transcluded in. 
>>
>> So in edit template, I want a list at the bottom of the tiddlers tagged 
>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
>> already transcluded in the current tiddler. That way I can see which 
>> tiddlers still need transcluding.
>>
>> Thanks for any help with this. It doesn't look very straightforward. 
>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
>> Maybe in 5.1.25?
>>
>> Blessings,
>>
>

-- 
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/1bb93689-4995-4b24-aa89-bd7312a4cff3n%40googlegroups.com.

Re: [tw5] Re: Filter request: "except those transcluded in the" current tiddler

[David Gifford]

Yes! A big "¡Sí!" to si! Thanks, works great!




On Wed, Jun 16, 2021 at 9:27 AM Si  wrote:

> Hi David,
>
> I've been planning to do something similar in my own wiki. I can't think
> of a way to do it with a single filter expression, but here is a very
> clunky approach:
>
> <$list filter="[tag] [tag{!!draft.of}]"
> variable=tagged-tiddler>
> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]]
> }}}>
> <$list filter="[!search]">
> <$link to=<>><>
> 
> 
> 
> 
>
> This should work in both edit and view mode, but you can easily simplify
> the first filter expression if you only need it to work in edit mode.
>
> There's probably a more elegant approach out there but this seems to work.
>
> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>
>> Hi all
>>
>> I need another list filter:
>>
>> ...minus any tiddlers transcluded in the" current tiddler.
>>
>> Use case: I plan to use transclusions to build long "article" tiddlers,
>> with section headers and specific ordering of the transclusions. But as I
>> take notes, I want to tag note tiddlers with the article(s) they will be
>> transcluded in.
>>
>> So in edit template, I want a list at the bottom of the tiddlers tagged
>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have
>> already transcluded in the current tiddler. That way I can see which
>> tiddlers still need transcluding.
>>
>> Thanks for any help with this. It doesn't look very straightforward.
>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet.
>> Maybe in 5.1.25?
>>
>> Blessings,
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/EnyDD7GseG0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/d70cb040-fa23-407b-9dcd-c9edf4b36210n%40googlegroups.com
> 
> .
>

-- 
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/CANE%3DBF%2B4-i30-6nuCm%2BFNED_XauwvwMs1x1ewv5K-FSY2MrZ%3DQ%40mail.gmail.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Si]

Just realized the search filter should probably be more like this: 
[!search:text:literal,casesensitive]

On Wednesday, 16 June 2021 at 15:27:16 UTC+1 Si wrote:

> Hi David,
>
> I've been planning to do something similar in my own wiki. I can't think 
> of a way to do it with a single filter expression, but here is a very 
> clunky approach:
>
> <$list filter="[tag] [tag{!!draft.of}]" 
> variable=tagged-tiddler>
> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
> }}}>
> <$list filter="[!search]">
> <$link to=<>><>
> 
> 
> 
> 
>
> This should work in both edit and view mode, but you can easily simplify 
> the first filter expression if you only need it to work in edit mode.
>
> There's probably a more elegant approach out there but this seems to work.
>
> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>
>> Hi all
>>
>> I need another list filter:
>>
>> ...minus any tiddlers transcluded in the" current tiddler.
>>
>> Use case: I plan to use transclusions to build long "article" tiddlers, 
>> with section headers and specific ordering of the transclusions. But as I 
>> take notes, I want to tag note tiddlers with the article(s) they will be 
>> transcluded in. 
>>
>> So in edit template, I want a list at the bottom of the tiddlers tagged 
>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
>> already transcluded in the current tiddler. That way I can see which 
>> tiddlers still need transcluding.
>>
>> Thanks for any help with this. It doesn't look very straightforward. 
>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
>> Maybe in 5.1.25?
>>
>> Blessings,
>>
>

-- 
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/d71adc8d-d455-402a-b404-7cd6a50e0428n%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Si]

Just realised the search should be literal and case sensitive: 
[!search::literal,casesensitive]
On Wednesday, 16 June 2021 at 15:27:16 UTC+1 Si wrote:

> Hi David,
>
> I've been planning to do something similar in my own wiki. I can't think 
> of a way to do it with a single filter expression, but here is a very 
> clunky approach:
>
> <$list filter="[tag] [tag{!!draft.of}]" 
> variable=tagged-tiddler>
> <$vars search-term={{{ [addprefix[{{]addsuffix[}}]] 
> }}}>
> <$list filter="[!search]">
> <$link to=<>><>
> 
> 
> 
> 
>
> This should work in both edit and view mode, but you can easily simplify 
> the first filter expression if you only need it to work in edit mode.
>
> There's probably a more elegant approach out there but this seems to work.
>
> On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:
>
>> Hi all
>>
>> I need another list filter:
>>
>> ...minus any tiddlers transcluded in the" current tiddler.
>>
>> Use case: I plan to use transclusions to build long "article" tiddlers, 
>> with section headers and specific ordering of the transclusions. But as I 
>> take notes, I want to tag note tiddlers with the article(s) they will be 
>> transcluded in. 
>>
>> So in edit template, I want a list at the bottom of the tiddlers tagged 
>> to the current tiddler [all[current]tagging[]], minus the tiddlers I have 
>> already transcluded in the current tiddler. That way I can see which 
>> tiddlers still need transcluding.
>>
>> Thanks for any help with this. It doesn't look very straightforward. 
>> There doesn't seem to be a way to do -[all[current]transcluding[]] yet. 
>> Maybe in 5.1.25?
>>
>> Blessings,
>>
>

-- 
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/e3d14bdf-ced2-455e-b2a1-aecc6745bf4dn%40googlegroups.com.

[tw5] Re: Filter request: "except those transcluded in the" current tiddler

[Si]

Hi David,

I've been planning to do something similar in my own wiki. I can't think of 
a way to do it with a single filter expression, but here is a very clunky 
approach:

<$list filter="[tag] [tag{!!draft.of}]" 
variable=tagged-tiddler>
<$vars search-term={{{ [addprefix[{{]addsuffix[}}]] }}}>
<$list filter="[!search]">
<$link to=<>><>





This should work in both edit and view mode, but you can easily simplify 
the first filter expression if you only need it to work in edit mode.

There's probably a more elegant approach out there but this seems to work.

On Tuesday, 15 June 2021 at 15:36:39 UTC+1 David Gifford wrote:

> Hi all
>
> I need another list filter:
>
> ...minus any tiddlers transcluded in the" current tiddler.
>
> Use case: I plan to use transclusions to build long "article" tiddlers, 
> with section headers and specific ordering of the transclusions. But as I 
> take notes, I want to tag note tiddlers with the article(s) they will be 
> transcluded in. 
>
> So in edit template, I want a list at the bottom of the tiddlers tagged to 
> the current tiddler [all[current]tagging[]], minus the tiddlers I have 
> already transcluded in the current tiddler. That way I can see which 
> tiddlers still need transcluding.
>
> Thanks for any help with this. It doesn't look very straightforward. There 
> doesn't seem to be a way to do -[all[current]transcluding[]] yet. Maybe in 
> 5.1.25?
>
> Blessings,
>

-- 
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/d70cb040-fa23-407b-9dcd-c9edf4b36210n%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[Saq Imtiaz]

@pmario thank you for taking a look. Oddly enough, this came up now as I 
was trying to see if I could replace a custom filter with the new filter 
capabilities in the core.

There are actually multiple ways that we could address this with a new 
filter but I haven't had the chance to think through them and figure out 
which would have the most universal utility. I'll post something on Github 
when I get the chance. 

Thank you.


On Wednesday, June 16, 2021 at 8:39:24 AM UTC+2 PMario wrote:

> Hi Saq,
> That's a tricky filter. You use the capability of the "reduce" filter, 
> that it has access to the "currentTiddler" inside the filter run. 
>
> If "elseXX" would have the same info it would be as simple as this. 
>
> [tag[Widgets]] +[get[caption]elseXX{!!title}]
>
> I think, the usecase is "generic" enough, to discuss a new elseX operator, 
> that has this info.
>
> Just a thought
> -mario
>

-- 
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/3ef8a992-d0e3-442b-aefa-ca2ec65ba2bfn%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[Saq Imtiaz]

 

> Am I correct ? I think this is behind the problem you have of 
> simplification. Otherwise this would be sufficient 
> [tag[Widgets]get[caption]else[title]]
>

I am at a loss as to what you are trying to say here. The filter you 
provide however would not under any circumstance return the desired result, 
even if you changed [title] to {!!title}.
 

> If you are prepared to split selection and display (in your case no) or 
> nest lists there is not problem. We could write a macro with two filters, 
> one selection one display and this would not be an issue.
>

I believe I have explained quite clearly that it isn't always a matter of 
choice to split things, or even as simple as demarcating things into just 
selection and display.  Furthermore, there isn't any problem to start with. 
My first post already contains a filter expression that returns the desired 
result. I wanted to see if someone could spot a simpler filter that might 
do the same trick. I would welcome any input along those lines within the 
stated constraints, otherwise I don't see any reason to continue this 
discussion. 

-- 
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/1c3f4f95-fa6d-47e3-a5b3-b2f6f17a250an%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[PMario]

Hi Saq,
That's a tricky filter. You use the capability of the "reduce" filter, that 
it has access to the "currentTiddler" inside the filter run. 

If "elseXX" would have the same info it would be as simple as this. 

[tag[Widgets]] +[get[caption]elseXX{!!title}]

I think, the usecase is "generic" enough, to discuss a new elseX operator, 
that has this info.

Just a thought
-mario

-- 
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/78db5c54-bfbb-41da-9122-5b3da7be2285n%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Saq,

Am I correct ? I think this is behind the problem you have of 
simplification. Otherwise this would be sufficient 
[tag[Widgets]get[caption]else[title]]

Typically a filter returns a list of titles, even if they are virtual, 
strings that are not actual tiddlers. operators permit references to other 
values such as tiddler content, variables and fields. These allow complex 
conditional selections or titles to be generated. The filter functionality 
has being developed much further so the output of run can be numbers, 
modified strings and titles etc... The result of  filter in the list widget 
is returned via the currentTiddler/named Variable or the emptyMessage ONLY. 

>From the above we can process each title and reference each titles 
additional content using the title as a key. For example we can access the 
caption in side the list {{!!caption}} this is the display process.

Since filters are so rich in functionality we can generate other lists, one 
may be a set of tiddlers with caption OR title as the output,  this is 
returned as the title via the currentTiddler/named Variable ONLY. Currently 
when you make this decision to extract secondary data in a filter you may 
loose access to the key (the tiddler title). The feature to do this is 
great but it is mixing the selection process with the display process. This 
is fine but presently the original tiddler title if present is lost as the 
display is the caption/title output not the always the title of the 
tiddler, you may loose the key.

Prerelease shows how a second value can be returned for each item in the 
list, in this case the counter number. In some filters it would be good if 
an additional variable that passed on the original tiddler title, in your 
example all  [tag[Widgets]]. sure some of these tiddlers will be 
eliminated, and there name not accessible, because the list never displays 
them, but the ones it does it would be useful. Sometimes the titles are 
virtual strings, but making these available may also be helpful.

If you are prepared to split selection and display (in your case no) or 
nest lists there is not problem. We could write a macro with two filters, 
one selection one display and this would not be an issue.

Is this in your problem scope?, or divergent?, What do you think?

Tones

On Tuesday, 15 June 2021 at 21:12:40 UTC+10 Saq Imtiaz wrote:

> @Tony
>
> Could you give some idea of how/why* It is going to be used in a context 
>> where other wikitext cannot be introduced. ?*
>>
>
> Explaining my specific use case would be quite complex as it is part of a 
> much larger application. The filter I've described in this thread is a 
> simpler one that presents an analogous issue, where you want to replace an 
> input title with one if its field if that field exists, otherwise retain 
> the original title. All without changing the list order. It could just as 
> easily be get[parent] instead of get[caption] if that helps with 
> conceptualizing the problem.
>
> There are plenty of general use cases where a filter needs to provide the 
> necessary output independently of other wikitext. For example:
>
>- As input to a widget that accepts a filter attribute.
>- In a configuration tiddler that accepts a filter. See for instance 
>$:/config/syncFilter or $:/core/ui/DefaultSearchResults.
>- As a filter meant to be used elsewhere via the subfilter[] operator
>- When trying to optimize refresh performance in a large and complex 
>widget tree and wanting to use as few widgets as possible.
>
> I am interested in the challenge.
>>
>
> A good way to frame the constraints is that it should be possible to type 
> the filter directly into the Filter tab in AdvancedSearch. 
>

-- 
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/81729bea-d24c-4a1b-b04d-24dcf28c47dan%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[Saq Imtiaz]

@Tony

Could you give some idea of how/why* It is going to be used in a context 
> where other wikitext cannot be introduced. ?*
>

Explaining my specific use case would be quite complex as it is part of a 
much larger application. The filter I've described in this thread is a 
simpler one that presents an analogous issue, where you want to replace an 
input title with one if its field if that field exists, otherwise retain 
the original title. All without changing the list order. It could just as 
easily be get[parent] instead of get[caption] if that helps with 
conceptualizing the problem.

There are plenty of general use cases where a filter needs to provide the 
necessary output independently of other wikitext. For example:

   - As input to a widget that accepts a filter attribute.
   - In a configuration tiddler that accepts a filter. See for instance 
   $:/config/syncFilter or $:/core/ui/DefaultSearchResults.
   - As a filter meant to be used elsewhere via the subfilter[] operator
   - When trying to optimize refresh performance in a large and complex 
   widget tree and wanting to use as few widgets as possible.

I am interested in the challenge.
>

A good way to frame the constraints is that it should be possible to type 
the filter directly into the Filter tab in AdvancedSearch. 

-- 
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/4c74d2d1-823d-4aef-85b7-d5e8b4f5c7cen%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Saq Et al,

Some thinking an experiments. I miss the TWC For Each Tiddler macro, which 
the following comes closer to. Such changes could be added to a new widget, 
as the ;list widget is busy, similar to the list Widget such as 
"list-report Widget", permitting more than one value to be extracted from 
inside the filter.

On prerelease we now have a counter variable which allows the following;
<$list filter="[tag[Widgets]sort[title]]" counter=item>
  <>. <$link/>


In the above you can see there are two variables available inside the list, 
the currentTiddler (or named variable)  and now the named counter in this 
case item.

The thing is we use the title or currentTiddler interchangeably with only 
one output. We can addprefixes and generate new tiddler titles, extract a 
field but do not have access to the tiddler title we used to generate it. I 
was thinking what if we could assign the currentTiddler (result) to a 
variable in a filter making the currentTiddler available in the 
list/template.

<$list filter="[tag[Widgets]sort[title]var:varname[]] 
+[get[caption]else{!!title}]">
  <> <>

OR
<$list filter="[tag[Widgets]sort[title]] :var:description{!!description}] 
+[get[caption]else{!!title}]">
   <> - <> 


In the Above cases for each iteration of the list the currentTiddler would 
be the caption or title, but varname would contain the original tiddler 
title, keeping in mind you may not see it if the given tiddler is 
eliminated from the output.

Basically for each iteration of the first run above the output title will 
be stored in varname and passed on to the next run.
If this could be done more than once a lot could be extracted from one list.

*Using counter*
You could actually use the counter (less 1) as the select value in a set 
statement, to turn the counter into a reference to a tiddler.

<$set name=widget-list filter="[tag[Widgets]sort[title]]">
<$list filter="[enlist]" counter=item>
  <>. <$link/> {{!!caption}}
''Use set select with filter=<> here!''



Tones
On Tuesday, 15 June 2021 at 10:37:02 UTC+10 TW Tones wrote:

> Saq,
>
> Could you give some idea of how/why* It is going to be used in a context 
> where other wikitext cannot be introduced. ?*
>
>- Do you want it in a "filtered transclusion"? see below
>
>
> Of course the following does what you want but the currentTiddler is not 
> available inside the list.
>
> <$list filter="[tag[Widgets]sort[title]] +[get[caption]else{!!title}]">
>
> 
>
> This also achieves the same?
> In the template you have access to the current tiddler, in the same way as 
> my first response with an inline template?
>
> <$list filter="[tag[Widgets]sort[title]]" template="caption-or-title">
>
> 
>
> Where caption-or-title contains
> {{{ [all[current]get[caption]else{!!title}] }}}
>
> *In a filtered transclusion you can use a template*
> {{{ [tag[Widgets]sort[title]]||caption-or-title}}}
>
> I am interested in the challenge.
>
> Regards
> Tones
> On Tuesday, 15 June 2021 at 09:18:48 UTC+10 Saq Imtiaz wrote:
>
>>
>>> Is the demand for a single filter expression a needed constraint?
>>>
>>
>>  Yes. It is going to be used in a context where other wikitext cannot be 
>> introduced. 
>> It is possible with the filter expression I posted but I'm curious if 
>> I've missed a simpler solution.
>>
>

-- 
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/50892f56-e9a7-41ee-b645-16d391b33d2en%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Saq,

Could you give some idea of how/why* It is going to be used in a context 
where other wikitext cannot be introduced. ?*

   - Do you want it in a "filtered transclusion"? see below


Of course the following does what you want but the currentTiddler is not 
available inside the list.

<$list filter="[tag[Widgets]sort[title]] +[get[caption]else{!!title}]">



This also achieves the same?
In the template you have access to the current tiddler, in the same way as 
my first response with an inline template?

<$list filter="[tag[Widgets]sort[title]]" template="caption-or-title">



Where caption-or-title contains
{{{ [all[current]get[caption]else{!!title}] }}}

*In a filtered transclusion you can use a template*
{{{ [tag[Widgets]sort[title]]||caption-or-title}}}

I am interested in the challenge.

Regards
Tones
On Tuesday, 15 June 2021 at 09:18:48 UTC+10 Saq Imtiaz wrote:

>
>> Is the demand for a single filter expression a needed constraint?
>>
>
>  Yes. It is going to be used in a context where other wikitext cannot be 
> introduced. 
> It is possible with the filter expression I posted but I'm curious if I've 
> missed a simpler solution.
>

-- 
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/7c1970c2-eac7-45ff-ad25-94e6008be5ecn%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[Saq Imtiaz]

>
>
> Is the demand for a single filter expression a needed constraint?
>

 Yes. It is going to be used in a context where other wikitext cannot be 
introduced. 
It is possible with the filter expression I posted but I'm curious if I've 
missed a simpler solution.

-- 
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/d2f77ca1-ccf0-4c8b-8124-08e9a5724accn%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Opps  [all[current]get[caption]else{!!title}] 

On Tuesday, 15 June 2021 at 09:00:25 UTC+10 TW Tones wrote:

> Saq,
>
> Is the demand for a single filter expression a needed constraint?, because 
> a filtered transclusion can be used to display the caption or title? Or am 
> I missing something?
>
> <$list filter="[tag[Widgets]]">
>   <$link><$text text={{{ [all[current]get[caption]else[{!!title}]] 
> }}}/>
> 
>
> Whilst we can squeeze more out of filters it is easy to overloads them, In 
> my above list the list filter relates to the selection the filtered 
> transclusion to the display of the item. They are distinct functions and 
> need not be combined. 
>
> Regards
> Tones
>
> On Tuesday, 15 June 2021 at 00:08:58 UTC+10 Saq Imtiaz wrote:
>
>> I feel like there must be a very simple way to do this that I am missing.
>>
>> Given an ordered list of tiddler titles, in a *single filter expression*, 
>> replace the title with the caption if there is one, else keep the title - 
>> without changing the order.
>>
>> The only solution I came up with is convoluted (on pre-release):
>>
>> [tag[Widgets]] 
>> :reduce[get[caption]else{!!title}format:titlelist[]addprefix[ 
>> ]addprefix] +[enlist-input[]]
>>
>> where tag[Widgets] is a good stand-in for testing purposes for the 
>> ordered list, as not all of these tiddler on 
>> https://tiddlywiki.com/prerelease/ have captions but most do.
>> Is there a simpler alternative?
>>
>> Cheers,
>> Saq
>>
>

-- 
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/08d5a866-168d-4742-8f33-2d47dea4fa21n%40googlegroups.com.

[tw5] Re: Filter question: get caption else use title

[TW Tones]

Saq,

Is the demand for a single filter expression a needed constraint?, because 
a filtered transclusion can be used to display the caption or title? Or am 
I missing something?

<$list filter="[tag[Widgets]]">
  <$link><$text text={{{ [all[current]get[caption]else[{!!title}]] 
}}}/>


Whilst we can squeeze more out of filters it is easy to overloads them, In 
my above list the list filter relates to the selection the filtered 
transclusion to the display of the item. They are distinct functions and 
need not be combined. 

Regards
Tones

On Tuesday, 15 June 2021 at 00:08:58 UTC+10 Saq Imtiaz wrote:

> I feel like there must be a very simple way to do this that I am missing.
>
> Given an ordered list of tiddler titles, in a *single filter expression*, 
> replace the title with the caption if there is one, else keep the title - 
> without changing the order.
>
> The only solution I came up with is convoluted (on pre-release):
>
> [tag[Widgets]] 
> :reduce[get[caption]else{!!title}format:titlelist[]addprefix[ 
> ]addprefix] +[enlist-input[]]
>
> where tag[Widgets] is a good stand-in for testing purposes for the 
> ordered list, as not all of these tiddler on 
> https://tiddlywiki.com/prerelease/ have captions but most do.
> Is there a simpler alternative?
>
> Cheers,
> Saq
>

-- 
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/307867f4-4730-44cf-80cc-521d68ad9e8cn%40googlegroups.com.

Re: [tw5] Re: Filter operators: Official documentation

[Mohammad Rahmani]

Hi Mario,

Ah, I did not know that! Is there any reason for that? (missing purpose and
parameter in https://tiddlywiki.com/prerelease)



On Tue, May 25, 2021 at 8:10 PM PMario  wrote:

> The "operator" docs is a formal description. ... The (Examples) should be
> for the "understanding". ... The problem is, we do need more "real world"
> examples, + explanation. That's all.
>
> I think everyone is free to provide "pull requests" at GitHub, or post
> examples in the GG, that can be transferred to the docs.
>

That is true! Maybe the proposal by stobot above works here to have more
clear docs for newcomers!

>
>
> PRs are preferred, since it makes live much easier for developers.
>
> just my thougths
> mario
>
>
Thank you!



> --
> 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/c463570c-fd8f-4a6e-a13a-9f1cbe0f8ba2n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMAdPsZ8C-p0XsZ7gNqZezTM1dw_CVYsYE1xodpFan%3Dc%2BA%40mail.gmail.com.

[tw5] Re: Filter operators: Official documentation

[PMario]

The "operator" docs is a formal description. ... The (Examples) should be 
for the "understanding". ... The problem is, we do need more "real world" 
examples, + explanation. That's all. 

I think everyone is free to provide "pull requests" at GitHub, or post 
examples in the GG, that can be transferred to the docs. 

PRs are preferred, since it makes live much easier for developers. 

just my thougths
mario

-- 
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/c463570c-fd8f-4a6e-a13a-9f1cbe0f8ba2n%40googlegroups.com.

Re: [tw5] Re: Filter operators: Official documentation

[si]

@Mohammad I haven't read all of this thread, but I did notice that the 
descriptions of filter expressions in the pre-release documentation seem to 
be missing important info. Eg. they should have a "purpose" and "parameter" 
field: https://tiddlywiki.com/#putafter%20Operator
On Tuesday, 25 May 2021 at 16:18:24 UTC+1 Mohammad wrote:

> On Tue, May 25, 2021 at 4:55 PM TiddlyTweeter  wrote:
>
>> Ciao Mohammad
>>
>> It is an interesting issue. 
>>
>>- I AGREE the base docs are not enough for working everything out. 
>>
>>
>>- I DISAGREE that the solution to that problem should be in the main 
>>documentation!
>>
>>
> Let me think the problem is in the main documentation. From the filter 
> operator docs, I cannot understand what it does!
>
>  
>
>> WHY? 
>>
>> Because *IF *you added all possible combination examples it would 
>> inflate the main reference site, tiddlywiki.com, to be SO vast it would 
>> become unusable.
>>
>
> Agree! but I think the format of docs for filter ops need some more 
> clarification! See example in my above post!
>
> One other example
>
> subfilter="[tag[HelloThere]] +[putfirst[]]"
>
> Did you know, in the above example putfirst takes the last item of  
> [tag[HelloThere]] why? As a newbie how can I understand this?
>
>
> Another example
>
> putafter Operator
> 8th November 2015 at 8:48am
> Filter OperatorsListops OperatorsOrder Operators
> input  a list of items
> suffix  an integer N, 
> defaulting to 1
> output re-ordered list of items
> putafter what? I need to know putafter needs a filter
>
> [image: image.png]
>
>
>
>> IMO, Jeremy Ruston has done a very good job on documentation. 
>>
>
> You know, I am a big fan of TW!
>
>  
>
>>
>> It is true his style is somewhat gnostic :-)
>> The original minimalist! :-) 
>> But it is also true that he has ASTUTE BREVITY.
>>
>
> I think simple is the best but clear!
>
>>
>> IMO this issue should be about SECONDARY documentation.
>>
>
> I think we need to help.
>
>  
>
>>
>> At the moment everything focuses on tw.com. 
>> I'm NOT convinced that is the right approach for final practical, fully 
>> expanded, documentation.
>>
>> It seems to me that we need more DIFFERENTIATION.
>> AND recognizing better SUPPLEMENTARY documentation that covers specific 
>> aspects of TiddlyWiki in more detail would be best.
>>
>> I hope my points make sense, even if you don't agree.
>>
>
> Sure! Thank you
>
>> TT
>>
>>
>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/9b4500a8-cf8e-46f5-bdc4-2c8f66ff0269n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/9a60f668-6f2d-416d-abc4-b8cbba396201n%40googlegroups.com.

Re: [tw5] Re: Filter operators: Official documentation

[Mohammad Rahmani]

Hi Stobot,
You clearly explained the problem and have suggestions for improvement!


   1. I asked the question to see if the problem is only me or others have
   the same experiences.
   2. I do not expect the core developer to correct the docs as they are
   very busy!
   3. I think a better template for filter operator is needed in such a way
   newcomer can understand the syntax better
   4. I agree with your suggestion.

WE NEED TO HELP!



Best wishes
Mohammad


On Tue, May 25, 2021 at 4:05 PM Stobot  wrote:

> Mohammad, you point to something I personally agree is a learning curve
> (and I think unnecessarily so) for those who use similar "formula
> languages" to those I'm used to. My background is more Windows/Office
> stuff, so Excel, VBA, M, DAX, R, AutoIT etc. and there is typically a
> nearly standard way of documenting the functions (widgets in our case).
>
> They (like your example) start with a syntax string. I think this really
> helps illustrate better HOW to use it.
>
> For example the common XLOOKUP function in Excel is documented
> 
> like:
> =XLOOKUP(lookup_value, lookup_array, return_array, [if_not_found],
> [match_mode], [search_mode])
> ...and then immediately below that is a table with each of the parameters,
> whether they're required, what each option is and does, and what happens if
> it's omitted
> ...and then examples immediately follow (not sure why the TiddlyWiki
> examples are often (though not always) in separate tiddlers.
>
> Even just seeing in order how it's all pieced together, and then note the
> square bracket parameters which seems nearly universally to mean optional
> (at least in the languages described above). In some languages they even
> put the default right in the syntax line. That was Excel, but a similar
> pattern seems to be present in at least the other languages I use.
>
> So, for most widgets I'd suggest it would be easier to start with a
> similar syntax pattern before going into parameters. Now picking what
> brackets etc. to use in TiddlyWiki is a little more difficult since all of
> them are already actually used, but taking a crack at it... for example the
> <$wikify> would get a:
> *<$wikify name= text= [type= (default text/vnd.tiddlywiki)>]  [mode=]
> [output=] >*
> *Text where  is available*
> **
>

very nice!

> ... and then the table for each of those like the documentation already
> has largely.
>
> Now your example, a filter operator is slightly different, but a similar
> methodology could apply. Maybe include the whole list piece like you do
> already
> *<$list filter="[addsuffix]">*
> *The output of each input from the filter with the additional suffix*
> **
>

*<$list filter="[addsuffix:]">*
*The output of each input from the filter with the additional suffix*
**

yes, we have little chars to use for syntax demonstration for example
optional param, user given input, required param,...





> ... and then a table for input, suffix, and output. Input and output
> already have something, but a row for suffix could be there saying "string
> of text to add" or something.
>
> Anyways, I'm sure that can be refined, but circling back to your specific
> questions:
> 1. I don't have better resources, I find that the example pages are
> currently where I start (I guess because I think syntax first) and then
> come back
> 2. Experience seems similar to yours. I'm often very confused until I see
> enough examples (especially the ones with all of the colons - though love
> how powerful they are)
> 3. Above is at least an idea of how to improve
>

very nice!

>
>
> On Tuesday, May 25, 2021 at 1:42:38 AM UTC-4 Mohammad wrote:
>
>> I was reading the some filter operator they looks like this
>>
>> addsuffix Operator
>> 3rd February 2015 at 10:02pm
>> Filter OperatorsString Operators
>> input  a selection
>> of titles 
>> output the input, but with S added to the end of each title
>>
>> Examples
>> 
>>
>>
>> How can I realise I should use this filter operator like below:
>>
>>
>> <$list filter="[[inputlist]addsuffix[mysuffix]]">
>>
>> How should I understand it needs an input parameter which is different
>> from input from a previous step?
>>
>> In my opinion filter operators are an ESSENTIAL part of Tiddlywiki which
>> is also the most confusing part!
>>
>> My questions are:
>>
>> 1. DO you have better references for using and working with filters?
>> Please share links, resources, ...
>> 2. What is your experience using official documentation for filter
>> operators?
>> 3. How do you recommend to improve these documentations?
>>
>>
>> Some references to help improve the filter operators documentation
>>
>> [1]. TW-Scripts
>> [2]. 

Re: [tw5] Re: Filter operators: Official documentation

[Mohammad Rahmani]

On Tue, May 25, 2021 at 4:55 PM TiddlyTweeter 
wrote:

> Ciao Mohammad
>
> It is an interesting issue.
>
>- I AGREE the base docs are not enough for working everything out.
>
>
>- I DISAGREE that the solution to that problem should be in the main
>documentation!
>
>
Let me think the problem is in the main documentation. From the filter
operator docs, I cannot understand what it does!



> WHY?
>
> Because *IF *you added all possible combination examples it would inflate
> the main reference site, tiddlywiki.com, to be SO vast it would become
> unusable.
>

Agree! but I think the format of docs for filter ops need some more
clarification! See example in my above post!

One other example

subfilter="[tag[HelloThere]] +[putfirst[]]"

Did you know, in the above example putfirst takes the last item of
[tag[HelloThere]] why? As a newbie how can I understand this?


Another example

putafter Operator
8th November 2015 at 8:48am
Filter OperatorsListops OperatorsOrder Operators
input  a list of items
suffix  an integer N,
defaulting to 1
output re-ordered list of items
putafter what? I need to know putafter needs a filter

[image: image.png]



> IMO, Jeremy Ruston has done a very good job on documentation.
>

You know, I am a big fan of TW!



>
> It is true his style is somewhat gnostic :-)
> The original minimalist! :-)
> But it is also true that he has ASTUTE BREVITY.
>

I think simple is the best but clear!

>
> IMO this issue should be about SECONDARY documentation.
>

I think we need to help.



>
> At the moment everything focuses on tw.com.
> I'm NOT convinced that is the right approach for final practical, fully
> expanded, documentation.
>
> It seems to me that we need more DIFFERENTIATION.
> AND recognizing better SUPPLEMENTARY documentation that covers specific
> aspects of TiddlyWiki in more detail would be best.
>
> I hope my points make sense, even if you don't agree.
>

Sure! Thank you

> TT
>
>
> --
> 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/9b4500a8-cf8e-46f5-bdc4-2c8f66ff0269n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMB0N3_B7fqcM5rbFc592FVcFOi52SyFb3C8OH3v72f-Sg%40mail.gmail.com.

Re: [tw5] Re: Filter operators: Official documentation

[Mohammad Rahmani]

@Alvaro,
Thank you!  you explained what I mean


Best wishes
Mohammad


On Tue, May 25, 2021 at 5:35 PM Álvaro 
wrote:

> I agree, it is confusing especially if you don´t know/remember the filter
> sintax, in this case the filter steps. And how you say input is confusing
> if you don't know/remember that this input is the output of other filter
> step (or filter run). If i don't understand bad the list of titles between
> square bracket is a step. I like the idea the "constructor example" in a
> list (or in filtering transclusión), I don't know if it is better do it
> with styles in font or in a table. I think that also differenciate the
> parts of constructor, necessary vs optional.
>
> Also i agree with Stobot. "Example constructor" will be good point. I
> think also it happens with macro docs (for example in "toc" macro). I
> working in a macro and i doubt how write the optional parameters to do
> understandable to everyone.
>
> TiddlyTweeter, I agree with you in that brevety is good, but with some
> reminders it would be better and not much longer.
> El martes, 25 de mayo de 2021 a las 14:24:58 UTC+2, TiddlyTweeter escribió:
>
>> Ciao Mohammad
>>
>> It is an interesting issue.
>>
>>- I AGREE the base docs are not enough for working everything out.
>>
>>
>>- I DISAGREE that the solution to that problem should be in the main
>>documentation!
>>
>> WHY?
>>
>> Because *IF *you added all possible combination examples it would
>> inflate the main reference site, tiddlywiki.com, to be SO vast it would
>> become unusable.
>>
>> IMO, Jeremy Ruston has done a very good job on documentation.
>>
>> It is true his style is somewhat gnostic :-)
>> The original minimalist! :-)
>> But it is also true that he has ASTUTE BREVITY.
>>
>> IMO this issue should be about SECONDARY documentation.
>>
>> At the moment everything focuses on tw.com.
>> I'm NOT convinced that is the right approach for final practical, fully
>> expanded, documentation.
>>
>> It seems to me that we need more DIFFERENTIATION.
>> AND recognizing better SUPPLEMENTARY documentation that covers specific
>> aspects of TiddlyWiki in more detail would be best.
>>
>> I hope my points make sense, even if you don't agree.
>> TT
>>
>>
>> --
> 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/6392aca0-770a-4ccc-9d3c-42f503e68d88n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMAV0jNE51vJ9YY9eVZejC-Vc1VD%2BGxgND%2BhJqSzsuNk4g%40mail.gmail.com.

Re: [tw5] Re: Filter operators: Official documentation

[Mohammad Rahmani]

Hi Saq,


On Tue, May 25, 2021 at 5:59 PM Saq Imtiaz  wrote:

> @Mohammad
>
> <$list filter="[[inputlist]addsuffix[mysuffix]]">
>>
>> How should I understand it needs an input parameter which is different
>> from input from a previous step?
>>
>>
> Can you please explain what you mean here? I have re-read it a few times
> and don't understand.
> Thank you.
>


I mean this https://tiddlywiki.com/prerelease/#Filter%20Parameter
The reader cannot understand below logic for the
addprefix Operator
3rd February 2015 at 9:48pm
Filter OperatorsString Operators
input  a selection of
titles 
output the input, but with S added to the start of each title
you have  filter-ops

Example (only demo):
input: [tag[HelloThere]]
filter-op: addprefix
filter-param: student

then

<$list filter="[tag[Hellothere]addprefix[*student*]" 





> --
> 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/ed6d50a4-3a3a-43df-b439-4e78dbd20eb0n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMAywEr41RAMMQLHKowD5BMm%3Dp-a2GicPuYa%3DkKn-ENkUg%40mail.gmail.com.

[tw5] Re: Filter operators: Official documentation

[Saq Imtiaz]

@Mohammad

<$list filter="[[inputlist]addsuffix[mysuffix]]">
>
> How should I understand it needs an input parameter which is different 
> from input from a previous step?
>
>
Can you please explain what you mean here? I have re-read it a few times 
and don't understand.
Thank you. 

>

-- 
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/ed6d50a4-3a3a-43df-b439-4e78dbd20eb0n%40googlegroups.com.

[tw5] Re: Filter operators: Official documentation

[Álvaro]

 I agree, it is confusing especially if you don´t know/remember the filter 
sintax, in this case the filter steps. And how you say input is confusing 
if you don't know/remember that this input is the output of other filter 
step (or filter run). If i don't understand bad the list of titles between 
square bracket is a step. I like the idea the "constructor example" in a 
list (or in filtering transclusión), I don't know if it is better do it 
with styles in font or in a table. I think that also differenciate the 
parts of constructor, necessary vs optional.

Also i agree with Stobot. "Example constructor" will be good point. I think 
also it happens with macro docs (for example in "toc" macro). I working in 
a macro and i doubt how write the optional parameters to do understandable 
to everyone.

TiddlyTweeter, I agree with you in that brevety is good, but with some 
reminders it would be better and not much longer.
El martes, 25 de mayo de 2021 a las 14:24:58 UTC+2, TiddlyTweeter escribió:

> Ciao Mohammad
>
> It is an interesting issue. 
>
>- I AGREE the base docs are not enough for working everything out. 
>
>
>- I DISAGREE that the solution to that problem should be in the main 
>documentation!
>
> WHY? 
>
> Because *IF *you added all possible combination examples it would inflate 
> the main reference site, tiddlywiki.com, to be SO vast it would become 
> unusable.
>
> IMO, Jeremy Ruston has done a very good job on documentation. 
>
> It is true his style is somewhat gnostic :-)
> The original minimalist! :-) 
> But it is also true that he has ASTUTE BREVITY.
>
> IMO this issue should be about SECONDARY documentation.
>
> At the moment everything focuses on tw.com. 
> I'm NOT convinced that is the right approach for final practical, fully 
> expanded, documentation.
>
> It seems to me that we need more DIFFERENTIATION.
> AND recognizing better SUPPLEMENTARY documentation that covers specific 
> aspects of TiddlyWiki in more detail would be best.
>
> I hope my points make sense, even if you don't agree.
> TT
>
>
>

-- 
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/6392aca0-770a-4ccc-9d3c-42f503e68d88n%40googlegroups.com.

[tw5] Re: Filter operators: Official documentation

[TiddlyTweeter]

Ciao Mohammad

It is an interesting issue. 

   - I AGREE the base docs are not enough for working everything out. 


   - I DISAGREE that the solution to that problem should be in the main 
   documentation!

WHY? 

Because *IF *you added all possible combination examples it would inflate 
the main reference site, tiddlywiki.com, to be SO vast it would become 
unusable.

IMO, Jeremy Ruston has done a very good job on documentation. 

It is true his style is somewhat gnostic :-)
The original minimalist! :-) 
But it is also true that he has ASTUTE BREVITY.

IMO this issue should be about SECONDARY documentation.

At the moment everything focuses on tw.com. 
I'm NOT convinced that is the right approach for final practical, fully 
expanded, documentation.

It seems to me that we need more DIFFERENTIATION.
AND recognizing better SUPPLEMENTARY documentation that covers specific 
aspects of TiddlyWiki in more detail would be best.

I hope my points make sense, even if you don't agree.
TT


-- 
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/9b4500a8-cf8e-46f5-bdc4-2c8f66ff0269n%40googlegroups.com.

[tw5] Re: Filter operators: Official documentation

[Stobot]

Mohammad, you point to something I personally agree is a learning curve 
(and I think unnecessarily so) for those who use similar "formula 
languages" to those I'm used to. My background is more Windows/Office 
stuff, so Excel, VBA, M, DAX, R, AutoIT etc. and there is typically a 
nearly standard way of documenting the functions (widgets in our case). 

They (like your example) start with a syntax string. I think this really 
helps illustrate better HOW to use it. 

For example the common XLOOKUP function in Excel is documented 

 
like: 
=XLOOKUP(lookup_value, lookup_array, return_array, [if_not_found], 
[match_mode], [search_mode])
...and then immediately below that is a table with each of the parameters, 
whether they're required, what each option is and does, and what happens if 
it's omitted
...and then examples immediately follow (not sure why the TiddlyWiki 
examples are often (though not always) in separate tiddlers. 

Even just seeing in order how it's all pieced together, and then note the 
square bracket parameters which seems nearly universally to mean optional 
(at least in the languages described above). In some languages they even 
put the default right in the syntax line. That was Excel, but a similar 
pattern seems to be present in at least the other languages I use. 

So, for most widgets I'd suggest it would be easier to start with a similar 
syntax pattern before going into parameters. Now picking what brackets etc. 
to use in TiddlyWiki is a little more difficult since all of them are 
already actually used, but taking a crack at it... for example the 
<$wikify> would get a:
*<$wikify name= text= [type=]  [mode=] 
[output=] >*
*Text where  is available*
**
... and then the table for each of those like the documentation already has 
largely.

Now your example, a filter operator is slightly different, but a similar 
methodology could apply. Maybe include the whole list piece like you do 
already
*<$list filter="[addsuffix]">*
*The output of each input from the filter with the additional suffix*
**
... and then a table for input, suffix, and output. Input and output 
already have something, but a row for suffix could be there saying "string 
of text to add" or something.

Anyways, I'm sure that can be refined, but circling back to your specific 
questions:
1. I don't have better resources, I find that the example pages are 
currently where I start (I guess because I think syntax first) and then 
come back
2. Experience seems similar to yours. I'm often very confused until I see 
enough examples (especially the ones with all of the colons - though love 
how powerful they are)
3. Above is at least an idea of how to improve


On Tuesday, May 25, 2021 at 1:42:38 AM UTC-4 Mohammad wrote:

> I was reading the some filter operator they looks like this
>
> addsuffix Operator
> 3rd February 2015 at 10:02pm
> Filter OperatorsString Operators
> input  a selection of 
> titles 
> output the input, but with S added to the end of each title
>
> Examples 
> 
>
>
> How can I realise I should use this filter operator like below:
>
>
> <$list filter="[[inputlist]addsuffix[mysuffix]]">
>
> How should I understand it needs an input parameter which is different 
> from input from a previous step?
>
> In my opinion filter operators are an ESSENTIAL part of Tiddlywiki which 
> is also the most confusing part!
>
> My questions are:
>
> 1. DO you have better references for using and working with filters? 
> Please share links, resources, ...
> 2. What is your experience using official documentation for filter 
> operators?
> 3. How do you recommend to improve these documentations?
>
>
> Some references to help improve the filter operators documentation
>
> [1]. TW-Scripts
> [2]. PowerSearch
> [3]. Grok Tiddlywiki
> [4]. Tobias Beer Filter References
> [5]. S.S draft for restructuring TW documentation
> [6]. Tones GitWiki
>
>
>
> Best wishes
> Mohammad
>

-- 
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/8698e7d4-be6d-4701-8a62-62077c9628a0n%40googlegroups.com.

Re: [tw5] Re: Filter question: !

[Mohammad Rahmani]

On Tue, May 18, 2021 at 5:15 AM TW Tones  wrote:

> Do look at this https://tiddlywiki.com/#Performance


Good point!

>
> [all[tiddlers]tag[x]!is[current].. may be better for performance even
> although there is a presumed all[] in your filter.
>

I like to have some good practice, and this seems one of them!

>
> Tones
>
> On Monday, 17 May 2021 at 21:11:00 UTC+10 PMario wrote:
>
>> Hi,
>> I think both are good. IMO it depends on your personal taste.
>>
>> Pereformace wise they should be very similar and the number is already
>> limited by [tag[new]
>> -m
>> On Monday, May 17, 2021 at 10:00:57 AM UTC+2 Atronoush wrote:
>>
>>>
>>>1. open https://tiddlywiki.com/
>>>2. create three tiddlers called Tid01 Tid02 Tid03 all tagged with new
>>>
>>>
>>> I wrote the below wikitext in *Tid01*
>>>
>>> <$list filter="[tag[new]!]">
>>>
>>> 
>>>
>>> In another test I wrote the below wikitext in *Tid01*
>>>
>>> <$list filter="[tag[new]!is[current]">
>>>
>>> 
>>>
>>>
>>> Both give the same result! Do you recommend the first snippets!
>>>
>>> --Atro
>>>
>> --
> 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/b6d3aed1-a025-4a09-b90d-7ed2c94622d1n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMDq7CsvXdKZYXA5fneWA54TH9JUNn7pRtaDPw_tXSWgnA%40mail.gmail.com.

[tw5] Re: Filter question: !

[TW Tones]

Do look at this https://tiddlywiki.com/#Performance

[all[tiddlers]tag[x]!is[current].. may be better for performance even 
although there is a presumed all[] in your filter.

Tones

On Monday, 17 May 2021 at 21:11:00 UTC+10 PMario wrote:

> Hi,
> I think both are good. IMO it depends on your personal taste. 
>
> Pereformace wise they should be very similar and the number is already 
> limited by [tag[new] 
> -m
> On Monday, May 17, 2021 at 10:00:57 AM UTC+2 Atronoush wrote:
>
>>
>>1. open https://tiddlywiki.com/
>>2. create three tiddlers called Tid01 Tid02 Tid03 all tagged with new
>>
>>  
>> I wrote the below wikitext in *Tid01* 
>>
>> <$list filter="[tag[new]!]">
>>
>> 
>>
>> In another test I wrote the below wikitext in *Tid01*
>>
>> <$list filter="[tag[new]!is[current]">
>>
>>  
>>
>>
>> Both give the same result! Do you recommend the first snippets!
>>
>> --Atro
>>
>

-- 
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/b6d3aed1-a025-4a09-b90d-7ed2c94622d1n%40googlegroups.com.

[tw5] Re: Filter question: !

[PMario]

Hi,
I think both are good. IMO it depends on your personal taste. 

Pereformace wise they should be very similar and the number is already 
limited by [tag[new] 
-m
On Monday, May 17, 2021 at 10:00:57 AM UTC+2 Atronoush wrote:

>
>1. open https://tiddlywiki.com/
>2. create three tiddlers called Tid01 Tid02 Tid03 all tagged with new
>
>  
> I wrote the below wikitext in *Tid01* 
>
> <$list filter="[tag[new]!]">
>
> 
>
> In another test I wrote the below wikitext in *Tid01*
>
> <$list filter="[tag[new]!is[current]">
>
>  
>
>
> Both give the same result! Do you recommend the first snippets!
>
> --Atro
>

-- 
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/b17d98f0-ef32-446a-832f-a973a27590d7n%40googlegroups.com.

Re: [tw5] Re: Filter question: Use :filter operator

[Mohammad Rahmani]

On Fri, May 14, 2021 at 10:39 PM Saq Imtiaz  wrote:

> I'm on a touch device and can't test what you posted but let me clarify my
> examples above to:


Thank you Saq,
This second example shows the same result and both show the TITLE of the
filter not url!
I got your point, it passes the title and keeps it by end! It does not
return the value!

Thank you for calcification!



>
> Another way to explain it is that:
> <$list filter="[get[text]] :filter[get[url]]">
> <>
> 
>
> is equivalent to:
>
> <$list filter="[get[text]]">
> <$list filter="[get[url]!is[blank]]" variable="null">
> >
> 
> 
>
> On Friday, May 14, 2021 at 7:57:57 PM UTC+2 Mohammad wrote:
>
>> Saq,
>>  Many thanks for the clarification and I read the document again!
>>
>>
>> On Fri, May 14, 2021 at 9:07 PM Saq Imtiaz  wrote:
>>
>>> Another way to explain it is that:
>>> <$list filter="[get[text]] :filter[get[url]]">
>>>
>>> 
>>>
>>> is equivalent to:
>>>
>>> <$list filter="[get[text]]">
>>> <$list filter="[get[url]!is[blank]]" variable="null">
>>>
>>> 
>>> 
>>>
>>>
>> This example is great! but for me they return two different results! That
>> was my confusion!
>>
>> I have attached a JSON test both above solutions!
>> Please try at https://tiddlywiki.com/prerelease/
>> and let me know if you see what I mean?
>>
>> [image: image.png]
>>
>> --
> 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/fe6301a7-f1e2-48e7-8f94-478cf6313088n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMCFEdR4Ytfh2OBhuYfF_x5ezfKa_1haU2tHd7YOTTcEqg%40mail.gmail.com.

Re: [tw5] Re: Filter question: Use :filter operator

[Saq Imtiaz]

I'm on a touch device and can't test what you posted but let me clarify my 
examples above to:

Another way to explain it is that:
<$list filter="[get[text]] :filter[get[url]]">
<>


is equivalent to:

<$list filter="[get[text]]">
<$list filter="[get[url]!is[blank]]" variable="null">
>



On Friday, May 14, 2021 at 7:57:57 PM UTC+2 Mohammad wrote:

> Saq,
>  Many thanks for the clarification and I read the document again!
>
>
> On Fri, May 14, 2021 at 9:07 PM Saq Imtiaz  wrote:
>
>> Another way to explain it is that:
>> <$list filter="[get[text]] :filter[get[url]]">
>>
>> 
>>
>> is equivalent to:
>>
>> <$list filter="[get[text]]">
>> <$list filter="[get[url]!is[blank]]" variable="null">
>>
>> 
>> 
>>
>>
> This example is great! but for me they return two different results! That 
> was my confusion!
>
> I have attached a JSON test both above solutions!
> Please try at https://tiddlywiki.com/prerelease/
> and let me know if you see what I mean?
>
> [image: image.png]
>
>

-- 
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/fe6301a7-f1e2-48e7-8f94-478cf6313088n%40googlegroups.com.

Re: [tw5] Re: Filter question: Use :filter operator

[Mohammad Rahmani]

Saq,
 Many thanks for the clarification and I read the document again!


On Fri, May 14, 2021 at 9:07 PM Saq Imtiaz  wrote:

> Another way to explain it is that:
> <$list filter="[get[text]] :filter[get[url]]">
>
> 
>
> is equivalent to:
>
> <$list filter="[get[text]]">
> <$list filter="[get[url]!is[blank]]" variable="null">
>
> 
> 
>
>
This example is great! but for me they return two different results! That
was my confusion!

I have attached a JSON test both above solutions!
Please try at https://tiddlywiki.com/prerelease/
and let me know if you see what I mean?

[image: image.png]

-- 
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/CAAV1gMAS_Rg5do%3D5_ebTUwcWjCHVcf3pMW-y5F832O7A5j_hqA%40mail.gmail.com.


filter-question.json
Description: application/json

Re: [tw5] Re: Filter question: Use :filter operator

[Saq Imtiaz]

Another way to explain it is that:
<$list filter="[get[text]] :filter[get[url]]">



is equivalent to:

<$list filter="[get[text]]">
<$list filter="[get[url]!is[blank]]" variable="null">




-- 
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/9d8e49e8-a494-4ee4-b193-dcb7219cf9acn%40googlegroups.com.

Re: [tw5] Re: Filter question: Use :filter operator

[Saq Imtiaz]

You are misunderstanding the purpose of :filter.

It is used to include or exclude titles from the previous run, based on 
whether this filter run returns a result or not. The same principle as the 
filter[] operator for which I recommend reading the docs as they mostly 
apply here too: https://tiddlywiki.com/#filter%20Operator
 

> <$list filter="[get[text]] :filter[get[url]]">
>
>
The first filter run says: get the text field from the tiddler whose title 
is in the variable tempTid
The second filter run says: exclude all titles from the previous run, if 
they do not have url field. 

:filter does NOT change the input titles, it only excludes or includes them 
in its output based on the result of its filter run.
 

-- 
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/4b32cfe5-d3d6-4053-918e-e833bf8c46ban%40googlegroups.com.

Re: [tw5] Re: Filter question: Use :filter operator

[Mohammad Rahmani]

On Fri, May 14, 2021 at 8:10 PM Saq Imtiaz  wrote:

> :filter does exactly that, it filters which titles from the previous run
> are included based on whether its run returns a value for that title or not.


But I cannot get the result by :filter, have you tried the below filter?

<$list filter="[get[text]] :filter[get[url]]">





>
> I think what you want is [get[text]get[url]]
>

Thanks Saq! sometimes I forgot things may be these are sign of alzheimer!

>
>
>
>

-- 
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/CAAV1gMBfBvBCYB373G%3DYy6cOCpo0aTae8%2B%2BdxX%2BojQeo-oe-hQ%40mail.gmail.com.

[tw5] Re: Filter question: Use :filter operator

[Saq Imtiaz]

:filter does exactly that, it filters which titles from the previous run 
are included based on whether its run returns a value for that title or not.

I think what you want is [get[text]get[url]]

On Friday, May 14, 2021 at 5:36:19 PM UTC+2 Mohammad wrote:

> *Issue with :filter operator*
>
> 1. The variable *temTid *refers to tiddler *xx/temp/data,*
> 2. Tiddler *xx/temp/data* in its text field stores the name of another 
> tiddler called *aiche.org *
> 3. The tiddler * aiche.org * has a field called url
>
> I want to retrieve the url value as below
>
> \define temTid()  xx/temp/data
> <$list filter="[get[text]] :filter[get[url]]">
>
> 
>
> The *:filter* doesn't work and the $list just returns the result of the 
> first part  [get[text]] 
> What do you think? (all of them are dynamic and the value changes in 
> different runs)
>
> I know I can do this in two separate steps! But I am looking for a one 
> step solution as above
>
>
> - Explanation
>
>
>- *xx/temp/data *(this is a tiddler)
>   - text:  aiche.org 
>-   *aiche.org  *(this is a tiddler)
>   - text: some text
>   - url: http:/aiche.org/blog  
>
>
>
>
> Best wishes
> Mohammad
>

-- 
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/fecbab6f-b908-434d-8389-0d809f0cfc79n%40googlegroups.com.

Re: [tw5] Re: filter question: which tiddler is newer

[Mohammad Rahmani]

On Wed, May 5, 2021 at 2:35 PM TW Tones  wrote:

> Or this;
>
> <$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]]
> +[!sort[modified]]">
><$link/> {{!!modified}}
> 
>
> ;Newer test
> <$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]]
> +[sort[modified]] +[last[]]">
>
> 
> ;Older test
> <$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]]
> +[sort[modified]] +[first[]]">
>
> 
>
> Tones
>

Thank you Tones! All works and are short!

>
> On Wednesday, 5 May 2021 at 17:05:03 UTC+10 Mohammad wrote:
>
>> Hi Saq,
>>
>> Very clever! Both works!
>>
>> On Wed, May 5, 2021 at 11:08 AM Saq Imtiaz  wrote:
>>
>>> Does this do what you need?
>>>
>>> Aa Bb +[nsort[modified]limit[1]]
>>>
>>>
>> I am wondering why we did not try this which was available from 2015? ;-)
>>
>>
>>
>>> Or try something like this in 5.1.24 pre-release:
>>>
>>> Aa Bb :sort:date[get[modified]] +[limit[1]]
>>>
>>
>> Great! So, we can use the new named prefix :sort?
>> Is it possible to have multiple steps filter like below
>>
>> filter1 :filter[step2]  :filter[step3]
>>
>>
>>
>>
>>
>>>
>>>
>>> See https://tiddlywiki.com/prerelease/#Sort%20Filter%20Run%20Prefix
>>> On Wednesday, May 5, 2021 at 7:41:37 AM UTC+2 Mohammad wrote:
>>>
 Back to winter 2019, when we were working on the Commander plugin we
 needed a comparison between two tiddlers to see which is greater. See [1]
 The best solution we found (by BTC) at that time was as below [2]
 (still works and is part of Commander)


 <$set name="tidBMod" value={{{ [[Bb]get[modified]] }}}>
 <$set name="tidAMod" value={{{ [[Aa]get[modified]] }}}>
 <$list filter="[] []
 +[nsort[]last[1]removesuffix]">
 Yes, Aa is newer
 
 <$list filter="[] []
 +[nsort[]last[1]removesuffix]">
 No, Aa is older
 
 
 


 With the advent of many new filter operator, I want to know if there is
 a shorter and more semantic solution can be found today Apr 2021

 I thought about the below solution and it works in TW 5.1.23

 <$vars dtb={{{[[Bb]get[modified]]}}}>

 <$list
 filter="[[Aa]get[modified]compare:integer:gtthen[Aa]else[Bb]]">
 <> is newer!
 

 


 But I am wondering if we could use :filter or some other operator to
 drop the $vars and dtb and perform the comparison in single $list
 Note Aa and Bb are two tiddlers



 Best wishes
 Mohammad

 [1] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/3AGSBBJKBgAJ
 [2] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/UbIgaSFSBgAJ

 --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/918a183b-82d2-411e-8896-06315800770bn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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/b408d343-a850-40b8-b515-0dd43a3739f9n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMBMFadK_%3DT62M0Eht4EMB5yoA%3DGmNyKUe7NPF3mVTvs5Q%40mail.gmail.com.

Re: [tw5] Re: filter question: which tiddler is newer

[Mohammad Rahmani]

On Wed, May 5, 2021 at 3:47 PM Saq Imtiaz  wrote:

> @Mohammad:
>
>
>> Great! So, we can use the new named prefix :sort?
>> Is it possible to have multiple steps filter like below
>>
>> filter1 :filter[step2]  :filter[step3]
>>
>>
> Yes multiple filter runs can be combined just as before (with +, ~ etc).
> Note that the input to each filter run is the output from the previous run.
>

Thank you for clarification!

> --
> 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/e4ad2412-2c12-46dc-94b1-ff69d7df7cf8n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMCk3qx1Vk9RJNsQt5EWxjY%2B2n7niq3oTLMD2Xn-2mWNvw%40mail.gmail.com.

Re: [tw5] Re: filter question: which tiddler is newer

[Mohammad Rahmani]

Hi Josiah,

On Wed, May 5, 2021 at 3:28 PM TiddlyTweeter 
wrote:

> Mohammad wrote:
>
>> Back to winter 2019, when we were working on the Commander plugin ...
>>
>
>  I like how you used the "Royal WE" :-) (
> https://en.wikipedia.org/wiki/Royal_we)
>

I laughed a lot on this! Very nice!

But this is a real `we`! See the
https://kookma.github.io/TW-Commander/#Acknowledgement
I remember how much people were kind to help to implement the Commander!
You did a great job
on regex! See help/regular expression in
https://kookma.github.io/TW-Commander/#%24%3A%2FCommander
which has been totally written by you!
Saq recently developed the Batch Edit button! Mark S did a lot of scripting
part! and BTC macros and help will always be appreciated in developing SNR.
I remember Watt who did a lot of testing and read docs for English!

Commander is a real example developed by a group of people here!
We were working together at that time and I appreciate all their talent,
time and kindness!




>
> Commander is brilliant! And basically YOU :-)
>

:-) :-)

Thank you





>
> Best wishes
> TT
>
>> --
> 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/0c0fd4dc-5570-47b7-9621-375c906f0289n%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMAFWWK9UAe3AYCC%2B8KH%3DNN0WYFooW9oSvNgRAeYxnfp7w%40mail.gmail.com.

[tw5] Re: "Filter Expression" doc

[Saq Imtiaz]

Joshua's reply is the best way to work with docs. However, if you aren't 
already using node and just want to make a PR for a single tiddler, you can 
do so via the Github web interface.

   - Find the tiddler you want to make a PR for at TiddlyWiki.com
   - From the tiddler toolbar choose the more dropdown arrow, then info.
   - Go to the Sources tab.
   - Follow the second link to Github.
   - Edit the tiddler on Github to make a PR. It is a good idea to do the 
   actual editing on TiddlyWiki.com and then copy and paste over your content 
   to the Github editor, preserving the metadata at the top of the tiddler.


On Tuesday, May 4, 2021 at 10:50:32 PM UTC+2 jn.pierr...@gmail.com wrote:

> Fine. How may I help then? It's also that bit that I find lacking in the 
> doc (just poke at it but got no interesting stuff for this).
>
> Le mardi 4 mai 2021 à 21:59:46 UTC+2, saq.i...@gmail.com a écrit :
>
>> I don't disagree. Contributions to the documentation are very welcome.
>>
>> On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:
>>
>>> right. not very user friendly. could be noted earlier at ~
>>>
>>> the same for the others. when there is so much to read, being kind on 
>>> the reader is not undue.
>>>
>>> Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :
>>>
 As the table indicates, :else is equivalent to the ~ filter run prefix 
 which is explained earlier in the same tiddler.

 On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com 
 wrote:

> In the "Filter Expression" tiddler the :enter prefix is not listed in 
> the first part, only given in a subsequent table.
>
> As such, :else lacks a proper explanation of what it does.
>


-- 
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/5bdfc085-2fe8-48d3-9608-9aa8bb627cb6n%40googlegroups.com.

Re: [tw5] Re: filter question: which tiddler is newer

[Saq Imtiaz]

@Mohammad:
 

> Great! So, we can use the new named prefix :sort?
> Is it possible to have multiple steps filter like below
>
> filter1 :filter[step2]  :filter[step3]
>
>
Yes multiple filter runs can be combined just as before (with +, ~ etc). 
Note that the input to each filter run is the output from the previous run. 

-- 
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/e4ad2412-2c12-46dc-94b1-ff69d7df7cf8n%40googlegroups.com.

[tw5] Re: filter question: which tiddler is newer

[TiddlyTweeter]

Mohammad wrote:

> Back to winter 2019, when we were working on the Commander plugin ...
>

 I like how you used the "Royal WE" :-) (
https://en.wikipedia.org/wiki/Royal_we)

Commander is brilliant! And basically YOU :-)

Best wishes
TT

>

-- 
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/0c0fd4dc-5570-47b7-9621-375c906f0289n%40googlegroups.com.

Re: [tw5] Re: filter question: which tiddler is newer

[TW Tones]

Or this;

<$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]] 
+[!sort[modified]]">
   <$link/> {{!!modified}}


;Newer test
<$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]] 
+[sort[modified]] +[last[]]">


;Older test
<$list filter="[[ActionDeleteTiddlerWidget]] [[ActionListopsWidget]] 
+[sort[modified]] +[first[]]">



Tones

On Wednesday, 5 May 2021 at 17:05:03 UTC+10 Mohammad wrote:

> Hi Saq,
>
> Very clever! Both works!
>
> On Wed, May 5, 2021 at 11:08 AM Saq Imtiaz  wrote:
>
>> Does this do what you need?
>>
>> Aa Bb +[nsort[modified]limit[1]]
>>
>>
> I am wondering why we did not try this which was available from 2015? ;-)
>
>  
>
>> Or try something like this in 5.1.24 pre-release:
>>
>> Aa Bb :sort:date[get[modified]] +[limit[1]]
>>
>
> Great! So, we can use the new named prefix :sort?
> Is it possible to have multiple steps filter like below
>
> filter1 :filter[step2]  :filter[step3]
>
>
>
>  
>
>>
>>
>> See https://tiddlywiki.com/prerelease/#Sort%20Filter%20Run%20Prefix
>> On Wednesday, May 5, 2021 at 7:41:37 AM UTC+2 Mohammad wrote:
>>
>>> Back to winter 2019, when we were working on the Commander plugin we 
>>> needed a comparison between two tiddlers to see which is greater. See [1]
>>> The best solution we found (by BTC) at that time was as below [2] (still 
>>> works and is part of Commander)
>>>
>>>
>>> <$set name="tidBMod" value={{{ [[Bb]get[modified]] }}}>
>>> <$set name="tidAMod" value={{{ [[Aa]get[modified]] }}}>
>>> <$list filter="[] [] 
>>> +[nsort[]last[1]removesuffix]">
>>> Yes, Aa is newer
>>> 
>>> <$list filter="[] [] 
>>> +[nsort[]last[1]removesuffix]">
>>> No, Aa is older
>>> 
>>> 
>>> 
>>>
>>>
>>> With the advent of many new filter operator, I want to know if there is 
>>> a shorter and more semantic solution can be found today Apr 2021
>>>
>>> I thought about the below solution and it works in TW 5.1.23
>>>
>>> <$vars dtb={{{[[Bb]get[modified]]}}}>
>>>
>>> <$list 
>>> filter="[[Aa]get[modified]compare:integer:gtthen[Aa]else[Bb]]">
>>> <> is newer!
>>> 
>>>
>>> 
>>>
>>>
>>> But I am wondering if we could use :filter or some other operator to 
>>> drop the $vars and dtb and perform the comparison in single $list
>>> Note Aa and Bb are two tiddlers
>>>
>>>
>>>
>>> Best wishes
>>> Mohammad
>>>
>>> [1] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/3AGSBBJKBgAJ
>>> [2] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/UbIgaSFSBgAJ
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/918a183b-82d2-411e-8896-06315800770bn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/b408d343-a850-40b8-b515-0dd43a3739f9n%40googlegroups.com.

[tw5] Re: "Filter Expression" doc

[Jean-Pierre Rivière]

Thank You Josh. I still have a question re

"Fork the TW5 repository to your own GitHub user account, and then clone it 
locally."

I thought I only had to clone the TW5 repository directly onto my system 
and have done my work here, and then present a pull request from here? I 
have to say, that I never used git other than locally for a single user 
setup (me). So it just may very well be my ignoring the proper ways.

Do you mean that under my github account I need to have a lidicated project 
(my-tw5%fork or such) and when at home I feel it's worth it, commit my 
local change to it and from it create a pull request to the main project?

regards,

-- 
Jean-Pierre

Le mercredi 5 mai 2021 à 01:13:42 UTC+2, joshua@gmail.com a écrit :

> Fork the TW5 repository to your own GitHub user account, and then clone it 
> locally. 
>
> Then checkout the "tiddlywiki-com" branch via git command line. (This 
> branch can live push updates to the website, and not wait until the next 
> Version release).
>
> Then, run the node command given in the `bin` scripts folder:
> `./path/to/TiddlyWiki5/bin.serve.sh`
>
> This launches the "tiddlywiki-com-server" Edition (from the 
> 'TiddlyWiki5/editions' folder) as a node process.
>
> Navigate a browser to 127.0.0.1:8080. Make changes to documentation 
> tiddlers. Push your changes back to your fork.
>
> From GitHub, create a Pull Request from your fork of the "tiddlywiki-com" 
> branch to the official repository's "tiddlywiki-com" branch. Describe your 
> changes in your PR.
>
> The community can then review those changes, and Jeremy can merge if it 
> all looks good.
>
> Best,
> Joshua Fontany
>
>
>
> On Tuesday, May 4, 2021 at 1:50:32 PM UTC-7 jn.pierr...@gmail.com wrote:
>
>> Fine. How may I help then? It's also that bit that I find lacking in the 
>> doc (just poke at it but got no interesting stuff for this).
>>
>> Le mardi 4 mai 2021 à 21:59:46 UTC+2, saq.i...@gmail.com a écrit :
>>
>>> I don't disagree. Contributions to the documentation are very welcome.
>>>
>>> On Tuesday, May 4, 2021 at 9:46:02 PM UTC+2 jn.pierr...@gmail.com wrote:
>>>
 right. not very user friendly. could be noted earlier at ~

 the same for the others. when there is so much to read, being kind on 
 the reader is not undue.

 Le mardi 4 mai 2021 à 21:30:54 UTC+2, saq.i...@gmail.com a écrit :

> As the table indicates, :else is equivalent to the ~ filter run prefix 
> which is explained earlier in the same tiddler.
>
> On Tuesday, May 4, 2021 at 9:09:23 PM UTC+2 jn.pierr...@gmail.com 
> wrote:
>
>> In the "Filter Expression" tiddler the :enter prefix is not listed in 
>> the first part, only given in a subsequent table.
>>
>> As such, :else lacks a proper explanation of what it does.
>>
>

-- 
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/efeccf52-71fa-4a16-969a-4b48ada4929an%40googlegroups.com.

Re: [tw5] Re: filter question: which tiddler is newer

[Mohammad Rahmani]

Hi Saq,

Very clever! Both works!

On Wed, May 5, 2021 at 11:08 AM Saq Imtiaz  wrote:

> Does this do what you need?
>
> Aa Bb +[nsort[modified]limit[1]]
>
>
I am wondering why we did not try this which was available from 2015? ;-)



> Or try something like this in 5.1.24 pre-release:
>
> Aa Bb :sort:date[get[modified]] +[limit[1]]
>

Great! So, we can use the new named prefix :sort?
Is it possible to have multiple steps filter like below

filter1 :filter[step2]  :filter[step3]





>
>
> See https://tiddlywiki.com/prerelease/#Sort%20Filter%20Run%20Prefix
> On Wednesday, May 5, 2021 at 7:41:37 AM UTC+2 Mohammad wrote:
>
>> Back to winter 2019, when we were working on the Commander plugin we
>> needed a comparison between two tiddlers to see which is greater. See [1]
>> The best solution we found (by BTC) at that time was as below [2] (still
>> works and is part of Commander)
>>
>>
>> <$set name="tidBMod" value={{{ [[Bb]get[modified]] }}}>
>> <$set name="tidAMod" value={{{ [[Aa]get[modified]] }}}>
>> <$list filter="[] []
>> +[nsort[]last[1]removesuffix]">
>> Yes, Aa is newer
>> 
>> <$list filter="[] []
>> +[nsort[]last[1]removesuffix]">
>> No, Aa is older
>> 
>> 
>> 
>>
>>
>> With the advent of many new filter operator, I want to know if there is a
>> shorter and more semantic solution can be found today Apr 2021
>>
>> I thought about the below solution and it works in TW 5.1.23
>>
>> <$vars dtb={{{[[Bb]get[modified]]}}}>
>>
>> <$list
>> filter="[[Aa]get[modified]compare:integer:gtthen[Aa]else[Bb]]">
>> <> is newer!
>> 
>>
>> 
>>
>>
>> But I am wondering if we could use :filter or some other operator to drop
>> the $vars and dtb and perform the comparison in single $list
>> Note Aa and Bb are two tiddlers
>>
>>
>>
>> Best wishes
>> Mohammad
>>
>> [1] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/3AGSBBJKBgAJ
>> [2] https://groups.google.com/g/tiddlywiki/c/9QQvkJkLogA/m/UbIgaSFSBgAJ
>>
>> --
> 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/918a183b-82d2-411e-8896-06315800770bn%40googlegroups.com
> 
> .
>

-- 
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/CAAV1gMCkyv%3DW03nw2-zLtru0hjFi2KJd8jiRfGSfSJH6dC3sSA%40mail.gmail.com.