Since the command history file is just a plain text file, user can edit the file outside of tinyTerm to put additional commands in the list for command auto-completion.
For example put all command TL1 commands in the history list to use as a dictionary.Ĭommand history file is not only used for auto completion, user interface options like window size, font size and font face, local edit mode, transparency are saved in the history file on exit, and loaded from the history file at next start. Plus the added Term and Script menu entries are saved in the history file too, so they can be restored at sebsequent sessions. To automate the execution of batch commands, simply drag and drop a list of commands from text editor, or select “Run…” from Script menu and select a text file with all the commands to be executed, tinyTerm send one command at a time, wait for prompt string before sending the next command, to avoid overflowing the receive buffer of the remote host or network device. Most command line interface system uses a prompt string to tell user it’s ready for the next command, for example “> “ or “$ “ used by Cisco routers. tinyTerm will auto detect the prompt string used by remote host when user is typing commands interactively, and use the detected prompt string during scripting. Additionally, prompt string can be set in the script using special command “!Prompt ”, refer to appendix A for details and other special commands supported for scripting.
0 kommentar(er)
