[Octave-bug-tracker] [bug #56625] debug prompt can change erratically

[John W. Eaton]

Follow-up Comment #6, bug #56625 (project octave):

Yes, it is confusing, so I think it is worth fixing so it behaves more
consistently.

I see now that the way the keyboard function enters the debugger is different
from what happens when it is entered on an error when debug_on_error is TRUE. 
When we enter the debugger because of an error, the debug_on_error state is
reset to FALSE.  When we enter with keyboard, it is not.  I think maybe the
correct thing to do is to set it to false any time we are at a debug or
keyboard prompt so that mistakes on those command lines don't push us into new
deeper debugging levels.  Maybe that fix alone would remove most of the
confusion?

I'll also take a look at the debug vs. keyboard prompt thing.  Maybe it would
be best just to use "debug> " (with a debugging level indicator) always
instead of trying to use "keyboard> "?  Or, just use "K>> " always if running
in --traditional mode?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56625>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/