5 ms·
> I mean, I've lived with XDG messing up where my config files are for several years Why don't you set your XDG vars to where you want to put them then? What'
by chimprich 4y ago
> I mean, I've lived with XDG messing up where my config files are for several years
Why don't you set your XDG vars to where you want to put them then?
What's your alternative? Force everyone to follow your preference instead of having it configurable?
- rkta 4y ago> Why don't you set your XDG vars to where you want to put them then? I hear that argument often. When a program uses $XDG_CONFIG_HOME/tool/ for its config files, to what value should I set XDG_CONFIG_HOME to get the old behavior where it puts its config in $HOME/.tool/?
- chimprich 4y agoThat's an interesting question, and I don't know the answer. A Google search and ChatGPT request provide no answers, so this seems like an uncommon request. It seems like there ought to be a way to achieve this reasonable request though. Possibly setting it to $HOME would make all/most programs assume that you wanted it to live in $HOME/.tool rather than $HOME/tool, but I'm guessing. I don't know if that's the standard.
- rkta 4y agoI'm not sure it is so uncommon - just that there is no answer. I'm pretty convinced that a lot less people would complain about the XDG Base Directory Specification if that would be possible. I'm one of those (though I usually do not publicly complain about it).