Engine:CCMD bind: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{dev/uiccmd}} Creates a new key binding, replacing existing key binding if any. <kua>bind Z "echo fred"</kua> == Arguments == * name - name of binding, which corresponds to a particular key, button, or other device. * value (optional) - script string or command to run. If not supplied, then prints the script or command value, if the binding exists. == Associations == *Key bindings are global, and not a part of any context. == Details == An 'alias' acts like a custom...") |
No edit summary |
||
| Line 11: | Line 11: | ||
== Details == | == Details == | ||
A 'bind' acts like a custom command for a key. It runs the assigned text as a script, which can contain a single-word command, statement, or script. | |||
Aliases do not have any parameters and will run the command, statement, or script verbatim. If for example, an alias named 'bob' is set to 'echo', it will always run exactly 'echo' which will print nothing, even if you run 'bob "some text". Here the second parameter was ignored. | Aliases do not have any parameters and will run the command, statement, or script verbatim. If for example, an alias named 'bob' is set to 'echo', it will always run exactly 'echo' which will print nothing, even if you run 'bob "some text". Here the second parameter was ignored. | ||
Revision as of 00:23, 15 October 2023
Creates a new key binding, replacing existing key binding if any.
bind Z "echo fred"
Arguments
- name - name of binding, which corresponds to a particular key, button, or other device.
- value (optional) - script string or command to run. If not supplied, then prints the script or command value, if the binding exists.
Associations
- Key bindings are global, and not a part of any context.
Details
A 'bind' acts like a custom command for a key. It runs the assigned text as a script, which can contain a single-word command, statement, or script.
Aliases do not have any parameters and will run the command, statement, or script verbatim. If for example, an alias named 'bob' is set to 'echo', it will always run exactly 'echo' which will print nothing, even if you run 'bob "some text". Here the second parameter was ignored.
Thus, aliases act like simple static macros. But when run they can do anything a script in the same context run by any other means could do. And because aliases are treated like commands, they can have direct key bindings.
Examples
Default values
- Check alias 'bob' for script value. No alias exists named 'bob'.
> alias bob Unknown: bob
- Call 'bob'. No command, variable or alias named 'bob' exist.
> bob Unknown: bob
- Create an alias 'bob' and set to 'echo fred'.
> alias bob "echo fred"
- Same as the second example, but now alias 'bob' exists. The 'echo' command in the 'bob' alias script runs, and prints 'fred'.
> bob fred
- Same as the first example, but now alias 'bob' exists and shows the value of the alias 'bob'
> alias bob
'bob' is 'echo fred'
To a variable
- 'bob' called without a value. No command, variable or alias named 'bob' exist.
> bob Unknown: bob
- Create an alias 'bob' and set to 'fred'.
> alias bob fred
- Same as the first example, but now alias 'bob' exists. The 'fred' command in the 'bob' alias script runs, and 'fred' doesn't exist.
> bob Unknown: fred
- Create variable 'fred'.
> var fred james
- Run 'bob'
> bob
'fred' is 'james'
- Try to set 'fred' through 'bob'. Value remains the same because 'bob' is only the statement "fred".
> bob alan
> bob
'fred' is 'james'