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

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

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


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #59331] Processor load stays up after `__run_test_suite__`
Date: Wed, 28 Oct 2020 09:17:29 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

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

Thanks for the explanation.  And no, we don't have anything for settings in
the interpreter other than the octaverc startup files.

Yes, I agree the current fix is fine for now and should be applied.

For the future, it would be good to think about a consistent, recommended way
to handle settings that

* belong primarily to the interpreter and might be reflected/cached in the
GUI
* belong primarily to the GUI and might be set/queried by the interpreter
* might belong somehow to both the interpreter and the GUI, be set from one or
the other, etc.

If the idea of a new terminal widget ever happens, I've also been thinking
about how the GUI and interpreter should really be connected and how startup
should happen, possibly by making it possible to start the GUI from the
interpreter command line.  But all of that is getting far away from the topic
of this report.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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