octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60122] Save and Run in editor does not always


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #60122] Save and Run in editor does not always save
Date: Tue, 11 May 2021 14:43:02 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #11, bug #60122 (project octave):

Torsten:  You might also try this change:


diff --git a/libgui/src/m-editor/file-editor.cc
b/libgui/src/m-editor/file-editor.cc
--- a/libgui/src/m-editor/file-editor.cc
+++ b/libgui/src/m-editor/file-editor.cc
@@ -666,6 +666,11 @@ namespace octave
        {
          // INTERPRETER THREAD
 
+         // Act as though this action was entered at the command propmt
+         // so that the interpreter will check for updated file time
+         // stamps.
+         Vlast_prompt_time.stamp ();
+
          tree_evaluator& tw = interp.get_evaluator ();
 
          if (tw.in_debug_repl ())


I'm not sure that is the correct place or if it would be better to put it in
the interpreter_event lambda function in main_window::run_file_in_terminal. 
Maybe it is needed in several more locations in the GUI?  Maybe it is even
something that should be done for all these interpreter callback events that
are the result of user interaction.  After all, these are similar to user
inputs at the command prompt, but entered using a button in the GUI instead of
a command in the terminal widget.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]