diff --git a/doc/todo/do_not_allow_using_stop_in_CommandPerform.mdwn b/doc/todo/do_not_allow_using_stop_in_CommandPerform.mdwn
index a6aeafdc83..353a273201 100644
--- a/doc/todo/do_not_allow_using_stop_in_CommandPerform.mdwn
+++ b/doc/todo/do_not_allow_using_stop_in_CommandPerform.mdwn
@@ -17,3 +17,20 @@ CommandPerform. Simply change the type:
 	+ stop :: CommandStart
 
 And follow the compile errors.
+
+> Hmm, I tried doing this, and I was not finding any other places
+> that stopped without emitting some kind of warning or informational
+> message.
+> 
+> And on second thought, this use of stop behaves the same as
+> `next (return False)`, or as having a CommandCleanup that
+> returns False without displaying any indication why.
+> 
+> So compprehensively fixing it would probably need to involve
+> returning something other than False from CommandCleanup, like a message
+> to display, but with only one case of the problem currently, I don't think it's
+> worth the bother to do that. Also, there are lots of different ways it
+> makes sense to display different messages in different situations and so 
+> returning a message to display feels wrong.
+> 
+> Guess I'm not going to do this. [[done]] --[[Joey]]