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

[Ahmed Othman]

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

I make modifications to some code and press run. 
The older version of the code (before modifications) is the one that is
actually running (according to the results).
The mark next to the file name indicates that the changes have been saved, but
the results are those corresponding to the older code.
Even if I press run again many times, the older code executes until I make
some more changes and press run again and then it executes the new code.

For example, I made a file named test.m with just one line of code "x=5". It
runs fine. If I change it to "x=2", I get x=5 in the terminal, even if I press
run multiple times, I still get x=5, until I modify it again by adding an
extra space for example,  it runs fine and I get x=2. 

This happens randomly (most of the time it works fine). But it is annoying
especially that sometimes I don't notice and get wrong results.

I noticed that it usually happens when I leave the code for a few minutes
between changes and doesn't happen if I make the modifications fast.

I am using octave 8.1.0 release on windows 10 (actually it always for me on
octave 6 and 7) and the files are saved locally on the hard drive.

[comment #19 comment #19:]
> @Ahmed - we haven't seen reoccurring reports of the same issue described in
the original post.  can you please add some detail to exactly what you're
seeing happen on your system?



    _______________________________________________________

Reply to this item at:

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

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