435dd97461
This is useful if you have a transcript of a user session and want to rerun those commands with RunCommandInterpreter. The same functionality is also useful in testing. I'm adding it primarily for the second reason. In a subsequent patch, I'm adding the ability to Python based commands to provide their "auto-repeat" command. Among other things, that will allow potentially state destroying user commands to prevent auto-repeat. Testing this with Shell or pexpect tests is not nearly as accurate or convenient as using RunCommandInterpreter, but to use that I need to allow auto-repeat. I think for consistency's sake, having interactive sessions always do auto-repeats is the right choice, though that's a lightly held opinion...
18 lines
519 B
OpenEdge ABL
18 lines
519 B
OpenEdge ABL
%feature("docstring",
|
|
"SBCommandInterpreterRunOptions controls how the RunCommandInterpreter runs the code it is fed.
|
|
|
|
A default SBCommandInterpreterRunOptions object has:
|
|
|
|
* StopOnContinue: false
|
|
* StopOnError: false
|
|
* StopOnCrash: false
|
|
* EchoCommands: true
|
|
* PrintResults: true
|
|
* PrintErrors: true
|
|
* AddToHistory: true
|
|
* AllowRepeats false
|
|
|
|
Interactive debug sessions always allow repeats, the AllowRepeats
|
|
run option only affects non-interactive sessions.
|
|
") lldb::SBCommandInterpreterRunOptions;
|