The debugger reads lines from stdin. The debugger supports command line editing when processing stdin if stdin is a terminal and the debugger variable $editline is non-zero. However, by default, $editline is zero, and the standard Command Prompt window's capabilities are used. If the debugger's line editing is needed, use the set command to change the setting, and set the terminal width to the correct value. After editing, press the Enter key to send the line to the debugger.
When you use the up and down arrow keys, the debugger skips duplicate commands. To see a complete list of the commands you have entered, use the history command.
The debugger copies each line from stdin to the record input file, if you have requested that file.
The debugger scans each line from the beginning, looking for backslash (\) characters, which 'quote' the immediately following character. If the line ends in a quoted newline, then another line is similarly processed from stdin and appended to the first one, with the quoted newline removed.
Whether or not command line editing is enabled, you can always use your terminal's cut-and-paste function to avoid excessive typing while entering input.
This section gives information about
History Replacement of the Line