Before, users must download an OS-specific config file and place it into one of several folders for the ArcCommander to work
This was, from a user's perspective, quite troublesome and annoying
Now the ArcCommander creates a global config file with default values in $XDG_HOME_CONFIG whenever the ArcCommander is used and a global config file is not present there
Due to legacy reasons, the ArcCommander still searches for the config file in those folders from before
With this, individual user settings set in previous ArcCommander versions can still be applied
$XDG_HOME_CONFIGwhenever the ArcCommander is used and a global config file is not present there