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. In the GUI, by default, $editline is zero, and the standard command prompt window's capabilities are used. If you are using the debugger's command-line mode, use the set command to change the setting, and set the terminal width to the correct value.
After editing, press Enter to send the line to the debugger.
-
Use the left and right arrow keys to edit parts of the line.
-
Use the up and down arrow keys to recall and edit earlier commands.
Note
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.
When input is recorded, the debugger copies each line from stdin to the file you select with the Start Command Recording dialog or the record input command.
The debugger scans each line from the beginning, looking for backslash (\) characters, which escape the subsequent character. If the line ends in an escaped newline, then another line is similarly processed from stdin and appended to the first one, with the escaped 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.