[Octave-bug-tracker] [bug #65499] Use separate GUI settings for Octave releases

[Markus Mützel]

Follow-up Comment #6, bug #65499 (group octave):

This might be a rather unusual use case: But I'm mostly running into this
issue when switching repeatedly between Qt5 and Qt6 with the same source tree
for testing.
Afaict, the changes proposed in comment #4 won't help for that use-case.

Having an environment variable that optionally overrides the path to the GUI
settings file might help. If that we had such an environment variable, we
could, e.g., set it in the `run-octave` script to point to a location in the
build tree if Octave is run before it is installed. That would probably help
with most of the issues I'm seeing personally.
I don't know if that would break the expected behavior for other developers
though.



    _______________________________________________________

Reply to this item at:

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

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