In Matlab, when editing and saving changes to a function/script while that is
debugged, leads to a dialog where ML asks to either skip saving or end
debugging. Indeed, when the file is saved the debug session is ended.
Octave allows to save the file being debugged and simply continues the debug
session. Sometimes, when typing dbquit or stepping through the file, I got
complaints about breakpoints not being found. AFAICS breakpoints are wiped
upon file save from the editor.
Should Octave mimic ML's behavior here? i.e.,
- recognize that the file is being debugged
- catch file save attempts and notify the user
- allow to save but then gracefully end the debug session.