|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #55822] GUI settings files do not honor XDG_CONFIG_HOME environment variable |
Date: | Wed, 6 Mar 2019 13:52:15 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36 |
Follow-up Comment #10, bug #55822 (project octave): Torsten - I looked into Qt and it does support XDG_CONFIG_HOME in a couple places, if that makes things easier or more portable. The QStandardPaths class honors it for ConfigLocation/GenericConfigLocation/AppConfigLocation. So for example 'QStandardPaths::writeableLocation (QStandardPaths::GenericConfigLocation)' returns XDG_CONFIG_HOME or ~/.config on GNU and Unixy systems, but it returns something else on macOS and Windows systems. The QSettings class also honors it when building the implied paths when you use the alternative org/app constructor you mentioned earlier. I think they both also support XDG_CONFIG_DIRS for reading settings from multiple system/user locations, as mentioned by Carnë, but that's a separate goal. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55822> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |