[Octave-bug-tracker] [bug #42705] Commands continue to be sent to the terminal if breakpoint hit

[Lachlan Andrew]

Follow-up Comment #10, bug #42705 (project octave):

Here is an updated changeset.

It deletes the script immediately after sourcing it.  One unexpected drawback
is that single-stepping through the code can no longer show the commands as
they are executed.

I modified the editor code so it doesn't prompt to re-create an empty file
with the name of the temporary script.  In doing so, I noticed that there are
two copies of the code that produce essentially the same dialog: one using
QMessageBox in file_editor::request_open_file  and one using uiwidget_creator
in octave_link::do_prompt_new_edit_file.  This is just like the case we have
with dbstop in bug #46795.  In the long term, I think we should have a way of
creating dialog boxes that doesn't depend so much on the context it is called
from.  Perhaps uiwidget_creator could be adapted to detect the context.

There is also conflict between two things galled "octave_link".  One is a
function that is octave's version of the "link" file system function call, and
the other links the GUI to Octave.  Dan might argue that it breaks modularity
to call file systems ops from the GUI.  I'm open to suggestions of how else to
generate the temporary script name.

(Sorry this comment is so long...)

(file #36285)
    _______________________________________________________

Additional Item Attachment:

File name: bug_42705_v1.cset              Size:4 KB


    _______________________________________________________

Reply to this item at:

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

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