[Octave-bug-tracker] [bug #59331] Processor load stays up after `__run_test_suite__`

[John W. Eaton]

Follow-up Comment #32, bug #59331 (project octave):

I was also able to duplicate the problem and the patch fixes it for me.

Adding the parameter to "notice_settings" seems like a reasonable fix to me
given that this setting appears to live in both the GUI and the interpreter. 
But would it be possible for it to be a property of the interpreter that is
simply reflected/cached in the GUI, similar to the way the current working
directory is?  Then, changing the setting in the GUI would trigger a call to
__mfile_encoding__ (as it does now) and that would use the event manager to
notify the GUI that the setting has been updated.  At that point, the GUI
would just cache the new value.  But maybe that is not possible (or easy)
given that the file encoding is stored inside the GUI settings data structure
and we aren't handling them individually, only as a group?

I'm not suggesting that we should handle all the GUI settings individually.  I
think the real problem is having settings that are stored in two places.  In
this case, the interpreter needs the encoding independent of the GUI, so it
seems that the interpreter should own that information and the GUI should be
able to set/get that value as needed?


    _______________________________________________________

Reply to this item at:

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

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