Indirect Command Files may be generated by two methods, using a normal text editor or by ``learning" from the Application Program. Learning is performed by responses prefixed with the letters ``{" and ``}". Detection of a response of the form:-
{Filename
will cause the specified File (with default file extension .UIC) to be opened to receive all further responses until such time as a response of the form:-
}
is received. This will cause the file to be closed and further input will not be saved (note however, that this ``}" character is saved within the file). A response of the form:-
{
is taken as implying that file UIPACK.UIC should be opened to receive all
subsequent responses. Note also that nesting is not allowed for ``Learning".
If UIPACK cannot open the requested Learn File (because of a bad filename
syntax or no write-access), an error message will be issued and the request
will be ignored. If the error occurs within a nested Command File, the Command
File Stack will be unwound and further input will be redirected to the keyboard.
Note that only the direct input from the Operator is saved in the learn file,
not any input from Indirect Command Files. Thus only the references to an
Indirect Command File (e.g. @filename) will be saved and not the contents
of the file.