Fix version numbers of from-version procedures

2026-08-06 10:58:54 +00:00 · 2025-11-22 11:20:15 +00:00
parent ac7837a98f
commit f2d5c2d83d
8 changed files with 8 additions and 8 deletions
@@ -14,7 +14,7 @@ In technical / logical terms:
 |`-[run]` |`:except[run]` |difference of sets |... AND NOT run |
 |`~[run]` |`:else[run]` |else |... ELSE run |
 |`=[run]` |`:all[run]` |union of sets without de-duplication |... OR run |
-|`=>[run]` |`:let[run]` |assign results to a variable |... LET run |
+|`=>[run]` |`:let[run]` |<<.from-version "5.4.0">> assign results to a variable |... LET run |

 The input of a run is normally a list of all the non-[[shadow|ShadowTiddlers]] tiddler titles in the wiki (in no particular order).<br>But the `+` prefix can change this:

@@ -1,5 +1,5 @@
 created: 20250307212252946
-from-version: 5.3.7
+from-version: 5.4.0
 modified: 20250307212252946
 rp-input: all titles from previous filter runs
 rp-output: an empty title list is always returned from the "let" filter run prefix
@@ -23,7 +23,7 @@ A named filter run prefix can precede any [[run|Filter Run]] of a [[filter expre
 [[<":or"> |"Or Filter Run Prefix"]] |
 [[<":reduce"> |"Reduce Filter Run Prefix"]] |
 [[<":sort">  /"v5.2.0"/ |"Sort Filter Run Prefix"]] |
-[[<":let">  /"v5.3.7"/ |"Let Filter Run Prefix"]] |
+[[<":let">  /"v5.4.0"/ |"Let Filter Run Prefix"]] |
 [[<":then">  /"v5.3.0"/ |"Then Filter Run Prefix"]]) [[run|"Filter Run"]]
 """/>

@@ -25,6 +25,6 @@ If a run has:

 * the prefix `=`, output titles are appended to the filter's output without de-duplication. <<.from-version "5.1.20">>

-* the prefix `=>`, the input is assigned to the variable named with the output title. <<.from-version "5.3.7">>
+* the prefix `=>`, the input is assigned to the variable named with the output title. <<.from-version "5.4.0">>

 {{Interchangeable Filter Run Prefixes}}
@@ -16,6 +16,6 @@ op-neg-output: the input, but with tiddler <<.place T>> filtered out if it exist

 <<.op title>> is a [[constructor|Selection Constructors]] (except in the form `!title`), but <<.olink2 "field:title" field>> is a [[modifier|Selection Constructors]].

-<<.from-version "5.3.7">> If the operand is quoted with round brackets then the <<.op title>> operator returns the complete list of titles assigned to the multi-valued variable. When negated, the title operator with multi-valued operands returns all the titles that are not present in the operand list.
+<<.from-version "5.4.0">> If the operand is quoted with round brackets then the <<.op title>> operator returns the complete list of titles assigned to the multi-valued variable. When negated, the title operator with multi-valued operands returns all the titles that are not present in the operand list.

 <<.operator-examples "title">>
@@ -9,7 +9,7 @@ type: text/vnd.tiddlywiki
 * A <<.def variable>> is a ''snippet of text'' that can be accessed by name
 * The text is referred to as the variable's <<.def value>>

-<<.from-version "5.3.7">> In ordinary usage, variables contain a single snippet of text. With the introduction of [[Multi-Valued Variables]] it is now possible to store a list of multiple values in a single variable. When accessed in the usual way, only the first value is returned, but using round brackets instead of the usual angle brackets retrieves the complete list of values. This makes the existence of multi-valued variables invisible unless you specifically need to use them.
+<<.from-version "5.4.0">> In ordinary usage, variables contain a single snippet of text. With the introduction of [[Multi-Valued Variables]] it is now possible to store a list of multiple values in a single variable. When accessed in the usual way, only the first value is returned, but using round brackets instead of the usual angle brackets retrieves the complete list of values. This makes the existence of multi-valued variables invisible unless you specifically need to use them.

 Variables are defined by [[widgets|Widgets]]. Several core widgets define variables, the most common being the <<.wlink LetWidget>>, <<.wlink SetWidget>> and <<.wlink ListWidget>> widgets.

@@ -25,7 +25,7 @@ In addition there are optional attributes that can be used:
 |$$message |A message to display as the title of the information logged. Useful when several `action-log` widgets are used in sequence. |
 |$$all |Set to "yes" to log all variables in a collapsed table. Note that if there is nothing specified to log, all variables are always logged instead.|

-<<.from-version "5.3.7">> Any [[multi-valued variables|Multi-Valued Variables]] or attributes are logged as a list of values.
+<<.from-version "5.4.0">> Any [[multi-valued variables|Multi-Valued Variables]] or attributes are logged as a list of values.

 <<.tip """A handy tip if an action widget is not behaving as expected is to temporarily change it to an `<$action-log>` widget so that the attributes can be observed.""">>

@@ -21,7 +21,7 @@ Attributes are evaluated in the order they are written. Attributes with the same

 ! Multi-Valued Variables

-<<.from-version "5.3.7">> The <<.wid let>> widget also allows [[multi-valued variables|Multi-Valued Variables]] to be set in one operation, each to the complete list of results obtained from evaluating an attribute.
+<<.from-version "5.4.0">> The <<.wid let>> widget also allows [[multi-valued variables|Multi-Valued Variables]] to be set in one operation, each to the complete list of results obtained from evaluating an attribute.

 Almost all operations that work with variables only consider the first item in the list. Using round brackets instead of angle brackets around the variable name gives access to the complete list of results. For example: