Some commands tend to run for a while, or keep running unintentionally when they fail.
At the point where one may want to edit such a command after it was executed, the log entry for starting the command (which can be used the jump to editing the command) is far enough down the log (or gone entirely) that the command list must be opened, searched, and the command opened for editing manually.
If the "Stopped command, ''" log entry could also be used to edit the command, that would be a handy shortcut in such a scenario.
EDIT: In v1.8.6.6, commands can now be edited from the "Stopped command" log entry, either by double-clicking or using the context menu