[Octave-bug-tracker] [bug #38982] Debugger re-executes previous command when typing only carriage-return

[Dan Sebald]

Follow-up Comment #2, bug #38982 (project octave):

OK, I can see that, at least in the case of "dbstep".  For other commands, I'm
not sure repeating the previous is helpful for much.  Can you think of any? 
Instead, it might be nicer to just map CR in debug mode to "dbstep".  For
example, one could then do


debug>> dbstep
debug>>
debug>>
debug>> disp(x)
debug>>
debug>> disp(y)
debug>>


instead of having to type


debug>> dbstep
debug>>
debug>>
debug>> disp(x)
debug>> dbstep
debug>> disp(y)
debug>> dbstep


Also, if there is the repeat command feature, what are your thoughts about
leaving debug-mode commands out of the command history?  It seems to me to be
convenient to not have those commands in the history because when I'm done
debugging chances are good I want to run the command again that triggers the
breakpoint and do some more debugging after I've made changes I think will fix
the problem.

I've argued in the past that any command that changes workspace memory should
be in the command history, and I think that is a good argument.  But in the
case of the debug repeat feature, we can't have a completely accurate
representation of the history.  One can't tell if the user typed:


debug>> dbstep
debug>>
debug>>
debug>> x = 3;
debug>> dbstep


or


debug>> dbstep
debug>> x = 3;
debug>> dbstep


as an example.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38982>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/