Hacker News new | ask | show | jobs
by m-n 1406 days ago
> I've gone so far as to keep my config directory visible -- ~/.config is a symlink to ~/config, which actually holds all my config, conveniently a git repository in itself for easy portability and tracking.

Sometimes I wonder how much defaulting to a directory with a leading dot hurt adoption. It gave me the impression that it was designed for or by people who don't manually edit their config files.
1 comments
bayindirh 1406 days ago
It's not defaulting to a directory, but to a variable: "$XDG_CONFIG_HOME".

Also, if you know how to change config of an application for the last 15-16 years, you also know that you're going to edit a "dot file".

KDE stored everything under ".kde" for a long long time, and stored a great tree under it too. rc files as config files and other KDE related files as app specific files.

In fact, the ".config" folder is just an evolution of ".kde" folder. Spec is written by KDE guys.

link
m-n 1406 days ago
> It's not defaulting to a directory, but to a variable: "$XDG_CONFIG_HOME".

By default I'm referring to the following part of the spec and the fact that systems I've used start in this state:

> If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.

link