Improve UX around running commands and exceptions

[dsmmcken]

Currently when you run a command, the "Running" button stays in line with the history. That is incorrect; the "Running" button should stay at the bottom so you know the command is still running. In addition, any exception that is the result of running the command should be printed at the bottom as well.

Example snippet (run in a Python console):

import time

for x in range(0, 100):
 print("Hello %d" % (x))

time.sleep(3)

print("Exception! %d" % (garbage))

When you run this, the "Running..." button gets pushed off the screen immediately. It then waits a few seconds, and the exception gets printed where the Running button was (off screen).

This makes it very confusing, as you may think the command is already completed successfully, but it is still running or has thrown an error.

In addition, it should only show "Running..." when it is actually the running command. Since commands run serially, only the actually running command should show running, any other queued commands should show queued. This also affects the startTime/endTime in the command history item - the elapsed time should be the time it took just to execute that command. Hitting cancel shouldn't remove the Running command until the cancellation has been confirmed.

[mofojed]

@dsmmcken How should we display the queued commands? Should the command still be printed out to the console history, and we just display "Queued" underneath it with the progress spinner? I could see that being annoying even if you have a couple commands queued stuck to the bottom, you wouldn't be able to see anything printing out to console (as it would be above). Or should they be horizontally stacked somehow or something?

[mofojed]

Assigned to @dsmmcken for spec