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

[Philip Nienhuis]

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

@Torsten:
First off, I don't know much about Qt and GUI development. So my perhaps naive
thinking goes as follows:

I don't follow the issue with e.g., editor styles in older Octave versions. At
first sight I'd think separate settings files per version would rather be
cleaner as they're not "polluted" (exaggerated term, sorry) with features that
don't exist across all Octave versions. Also, having stale settings from older
uninstalled Octave versions lingering on when using newer Octave doesn't sound
good to me either.

I thought about environment settings but I figured that how to invoke or
ignore them could be a challenge. In corporate settings/environments (sorry
for potential confusing terminology :-) ) environment settings could be made
inaccessible (immutable) for normal users.

A command line argument could be a first start for what I'd like to have.

Long time ago when Octave was started through a batch file I had
version-dependent settings files (named differently then IIRC) being copied
into place. Worked like a dream.
(a.o., indicating this isn't a recent wish :-) )

Anyway let's take adequate time to carefully think this over.



    _______________________________________________________

Reply to this item at:

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

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