Right now if no delay is specified for the .load command, it will use a delay of 25ms in between the execution of each line that it pushes through the REPL. While this works for most things, there will be obvious cases where more time than this will be needed to execute and get a return value from a line of code.
Instead of just blindly using 25ms, we should listen for the server's client's data event to know exactly when a response is returned, and then we should execute the next statement. This should only apply to situation where no delay is specified.
Closing this for now. I can't think of a practical use case where one wouldn't just specify a delay if they needed longer intervals. Will re-open if someone needs it.
Right now if no
delay
is specified for the.load
command, it will use a delay of 25ms in between the execution of each line that it pushes through the REPL. While this works for most things, there will be obvious cases where more time than this will be needed to execute and get a return value from a line of code.Instead of just blindly using 25ms, we should listen for the server's client's
data
event to know exactly when a response is returned, and then we should execute the next statement. This should only apply to situation where nodelay
is specified.