fix some typos

This commit is contained in:
pmario 2024-04-29 16:39:37 +02:00
parent d09ebe5668
commit ea8cfaffee
3 changed files with 16 additions and 14 deletions

View File

@ -19,15 +19,16 @@ System/Caption: System
System/Hint: Search for system tiddlers
System/Matches: //<small><<resultCount>> matches</small>//
Variables/Caption: Variables
Variables/Clear: Clear
Variables/Clear/Exclude: Clear exlude
Variables/Clear/Search: Clear search
Variables/Exclude: Exclude:
Variables/Exclude/Hide: Hide exclude input
Variables/Exclude/Hint: Filter eg: [prefix[.]]
Variables/Exclude/Save: Create Exclude Filter
Variables/Exclude/Save: Create exclude filter
Variables/Exclude/Show: Show exclude input
Variables/Exclude/Description: EDIT ME - Description is shown in the dropdown
Variables/ExpandAll: Expand All:
Variables/FoldAll: Fold All:
Variables/ExpandAll: Expand all:
Variables/FoldAll: Fold all:
Variables/Filter: Search:
Variables/Filter/Hint: Text eg: .attr
Variables/Hint: Filter global variables

View File

@ -1,5 +1,5 @@
created: 20240219185725834
modified: 20240221012350449
modified: 20240429134515751
tags: Features
title: VariableFormat
type: text/vnd.tiddlywiki
@ -10,11 +10,11 @@ Finding "self explaining" variable names for functions, procedures, widgets and
The <<.olink variables>> operator returns all "visible" variables from the current context, depending on where the filter run is executed. The <<.olink getvariable>> allows us to return the "text" or the "value" of variables. But this information is not enough to get a good understanding of existing variables.
So using <<.olink getvariables>> operator in combination with the <<.olink format>> operator we are able to improve information in variable listings.
So using <<.olink getvariable>> operator in combination with the <<.olink format>> operator we are able to improve information in variable listings.
|Token |Substituted Value |h
|`$type$` |variabe type eg: `\function`, `\procedure` and so on |
|`$name$` |returns the name of the variable |
|`$params$` |returns a list of parameters, which are defined with functions, procedures ... |
|`$firstLine$` |returns the first line of the variable content-type as used by <<.olink getvariables>> |
|`$firstLine$` |returns the first line of the variable content-type as used by <<.olink getvariable>> |
|`$varType$` |returns `var`, `fn`, ` proc`, ` macro` or ` widget` which can be used with the <<.olink variables>> operator |

View File

@ -1,6 +1,6 @@
caption: variables
created: 20190330100101453
modified: 20240219185349859
modified: 20240429134329720
op-input: ignored
op-output: the names of all the actively defined variables
op-parameter: <<.from-version "5.3.4">> whitespace separated list of variable-types
@ -25,13 +25,14 @@ type: text/vnd.tiddlywiki
The parameters <<.place T>> allow a "whitespace separated" list of variable codes that should be listed
* Default is all: `fn, var, proc, macro, widget`
* Default is `all` - `fn, var, proc, macro, widget`
* ''fn'' ... will only show variables defined as functions eg: `\function test-01()`
* ''var'' ... will only show standard variables defined with eg: `<$let test="test">...</$let>`
* ''proc'' ... will only show variables defined as procedures eg: `\procedure test-02()`
* ''macro'' ... will only show variables defined as macros eg: `\define test-macro()`
* ''widgets'' ... will only show variables defined as widgets eg: `\widget my-widget()`
* ''all'' ... If set it takes precedence and will show all variables
* ''fn'' ... Will only show variables defined as functions eg: `\function test-01()`
* ''var'' ... Will only show standard variables defined with eg: `<$let test="test">...</$let>`
* ''proc'' ... Will only show variables defined as procedures eg: `\procedure test-02()`
* ''macro'' ... Will only show variables defined as macros eg: `\define test-macro()`
* ''widgets'' ... Will only show variables defined as widgets eg: `\widget my-widget()`
<<.operator-examples "variables">>