@Albrecht-S Thanks again for the link. I had been collecting general use cases from stack overflow, but reading through the specs again, well, those cases are simply wrong. So the strategy is now: check if a prefs file or data directory exists in ~/.fltk/Vendor/Application, we will use that for everything. If not, we use $XDG_DATA_HOME/Vendor/Application/ (not fltk) for user data files, and $XDG_CONFIG_HOME/Vendor/Application.prefs are used for preferences.

As a precaution, I check for ~/, $HOME/, and ${HOME}/ at the start and replace them. I'll truncate at a possible :. If either of the environment variables are not set, I will use their respective default.

Porting would be done calling

mkdir ~/.local/share/Vendor/
mv ~/.fltk/Vendor/Application/ ~/.local/share/Vendor/
mv ~/.fltk/Vendor/ ~/.config/

Did I catch everything?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/303/1019370835@github.com>