|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #57235] Startup file .octaverc is always read in the system encoding |
Date: | Sat, 16 Nov 2019 11:36:49 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 |
Update of bug #57235 (project octave): Status: Ready For Test => Confirmed Summary: Character encoding problems => Startup file .octaverc is always read in the system encoding _______________________________________________________ Follow-up Comment #6: Re-titling to better reflect the remaining issue. I don't completely understand the Octave start-up process. But here is my analysis/guess of what is the issue: * The startup files are executed early on when initializing the interpreter. * The .m file encoding is restored from the value in the Qt settings file by the GUI process. * It looks like the latter is done after the startup files are executed. I don't know how this should be handled. Is there a settings file or something similar that holds properties for the interpreter (and not so much for the GUI)? CC'ing jwe because I think he best understands the startup process. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57235> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |