[Top][All Lists]

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

[Octave-bug-tracker] [bug #55855] GUI configuration files are not locate

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55855] GUI configuration files are not located following each platform's convention
Date: Thu, 7 Mar 2019 12:27:26 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Follow-up Comment #1, bug #55855 (project octave):

Another couple thoughts about choosing the directory:

* Do we care whether GUI configuration files are in the same directory as
octaverc files? On all platforms? I've learned that the ~/Library/Preferences
directory is used on macOS by Qt for QSettings, but that directory is
considered "hidden" by most macOS users, so shouldn't be used for
user-editable configuration files. So ~/.config/octave for user configuration
and ~/Library/Preferences/octave for GUI configuration on macOS?

* I'll probably be adding a library call to liboctave or liboctinterp that
will return the platform-dependent configuration directory for reading and
writing config files in the interpreter. This will probably *not* use
~/Library/Preferences. Once that exists that would be another alternative to
getting the configuration directory in libgui.

One downside to letting QSettings decide is that it uses the registry on
Windows instead of a real file if using NativeFormat.

But an advantage to use QSettings is the "Fallback Mechanism", that it can
read multiple system-wide and user-specific configuration sources and merge


Reply to this item at:


  Message sent via Savannah

reply via email to

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