[Octave-bug-tracker] [bug #39723] history commands lost when selecting block and right-clicking "Evaluate"

[Dan Sebald]

Follow-up Comment #2, bug #39723 (project octave):

Very creative solution given the constraints.  It works fairly well here, and
I'm inclined to say go with this because of the simplicity of it.

If I'm understanding correctly, the semaphore can remain within the GUI code
because of the callback mechanism.  That is, although the code looks like GUI
code it is really being executed from the worker thread.

I'm not a fan of waiting on things (in this case, the next evaluated command
is waiting for the previous to finish), but as I said, I don't think there is
much else that can be done with the setup as it is.  [The preference would be
to simply queue the command and when the result is complete a signal is
issued.]

I tried breaking things by evaluating long commands such as


for i=1:5000000; j=i; endfor
for i=1:5000000; j=i; endfor
for i=1:5000000; j=i; endfor
for i=1:5000000; j=i; endfor
for i=1:5000000; j=i; endfor
for i=1:5000000; j=i; endfor


and then try to inject other callback operations into the system like
breakpoints and directory changes.  It seems to behave fairly well, if only
freezing the system for a while.


    _______________________________________________________

Reply to this item at:

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

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