HEISENBERGM to linuxmemes@lemmy.world • 8 months agoHonestly it's a messlemmy.worldimagemessage-square41fedilinkarrow-up1624arrow-down113
arrow-up1611arrow-down1imageHonestly it's a messlemmy.worldHEISENBERGM to linuxmemes@lemmy.world • 8 months agomessage-square41fedilink
minus-squareDreamButtlinkfedilinkEnglish6•8 months agoEvery tool I build checks three places: An env variable (if it exists) which should point to a dir of the users choosing ~/.config/tool-name/ ~/.tool-name Which imo is how every modern application should work
minus-square@danAlink1•edit-28 months agoFor number 2, is it hard-coded to ~/.config or does it read XDG_CONFIG_HOME? The latter is what it should do, so that the user has the flexibility to move all their configs elsewhere.
minus-squareDreamButtlinkfedilinkEnglish1•8 months agoIt’s from $HOME so you would want to use the first option But it’s GTK that var is used by some people
minus-square@danAlink2•8 months agoPlease follow XDG specs and use $XDG_CONFIG_HOME instead of $HOME/.config. $HOME/.config could be a fallback if $XDG_CONFIG_HOME isn’t set. :)
Every tool I build checks three places:
Which imo is how every modern application should work
For number 2, is it hard-coded to
~/.configor does it readXDG_CONFIG_HOME? The latter is what it should do, so that the user has the flexibility to move all their configs elsewhere.It’s from $HOME so you would want to use the first option
But it’s GTK that var is used by some people
Please follow XDG specs and use
$XDG_CONFIG_HOMEinstead of$HOME/.config.$HOME/.configcould be a fallback if$XDG_CONFIG_HOMEisn’t set. :)