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: Markus Mützel
Subject: [Octave-bug-tracker] [bug #59331] Processor load stays up after `__run_test_suite__`
Date: Wed, 28 Oct 2020 09:07:19 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36 Edg/86.0.622.51

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

To give a little context how we ended up with the current situation:
The encoding setting originally was a setting only for the editor in the GUI.
The interpreter wasn't aware of encodings (which led to different issues).
When we added encoding-awareness to the interpreter, I thought it would make
sense to have the two settings synchronized. The reasoning being that a user
would probably expect that source files would be interpreted the same way as
they are displayed in the built-in editor.
When that happened, the GUI setting already existed. Looking back, it might
have made sense to move the setting from the GUI to the interpreter. But
afaict, there is no settings file (or something similar) that is read *before*
the first .m file is parsed. That would be a necessary requirement for this to
work correctly. The GUI settings seemed like a good replacement for that
missing(?) feature of the interpreter.

For Octave 6, Torsten's patch looks good to me imho.

But I agree that it might make sense to think about a better solution going
forward.


    _______________________________________________________

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]