Evaluate command: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
{| | {| | ||
|width=" | |width="125px"| '''Action:''' | ||
|width=" | |width="775px"| | ||
<span class="f_Para">Constructs and runs a Client command. The </span><span class="f_Monospace">evaluate</span><span class="f_Para"> argument values are concatenated into a single string and run as a Client command. </span> | <span class="f_Para">Constructs and runs a Client command. The </span><span class="f_Monospace">evaluate</span><span class="f_Para"> argument values are concatenated into a single string and run as a Client command. </span> | ||
Latest revision as of 21:20, 30 January 2023
Action: |
Constructs and runs a Client command. The evaluate argument values are concatenated into a single string and run as a Client command. Syntax: evaluate {&var|'string1'|"string2"|&&function} ... where:
No blanks are placed between the argument values when they are concatenated, so you may have to add blanks with quoted string values. Here is a macro definition that makes heavy use of the evaluate command: # historyButtons.macro: Assign extrabutton<extrBtn>-<extrBtn+3> # for history traversal # Usage: macro historyButtons <extrBtn> extraButtonBar main set &bnum = &argstring evaluate 'mapButton extrabutton' &bnum ' previousHistory' increment &bnum evaluate 'mapButton extrabutton' &bnum ' nextHistory' increment &bnum evaluate 'mapButton extrabutton' &bnum ' firstHistory' increment &bnum evaluate 'mapButton extrabutton' &bnum ' lastHistory' evaluate 'echo buttons ' &argstring '-' &bnum ' set for history' |
Client menu: | — |
Introduced: | Build 57 |