[Octave-bug-tracker] [bug #55178] Improved debug on error behaviour inside octave core functions

[Georg Wiora]

Follow-up Comment #17, bug #55178 (project octave):

@mmuetzel comment #14: I totally agree with you that showing the usage
information is superior over just throwing an error. If we would step back to
just throwing an error this would need a higher level of development on all
function to display proper error messages. This is unrealistic
(unfortunately).

My intention was to remove an annoying behavior while debugging, especially
interactively. It happens quite often that I enter an incorrect statement and
then have to close the print_usage window, step up the stack manually to come
back to my original position and try again. Just too many steps. 

An alternative to my suggestion would be a drop down selector for stack level
in the GUI as you proposed in comment #9. I am open for anything that
simplifies working with octave.

    _______________________________________________________

Reply to this item at:

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

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