4 ms·
One directory, maybe .config, seems like a good idea. One file is asking for trouble. All it takes is someone writing their first command-line app mixing up > a
by ksenzee 6y ago
One directory, maybe .config, seems like a good idea. One file is asking for trouble. All it takes is someone writing their first command-line app mixing up > and >> and suddenly the user's config for every tool they use is gone.
- _ZeD_ 6y agoIt should be versioned, so it requires a little more effort to be destroyed
- dmurray 6y agoBut some (most) config belongs in version control, and other parts are environment-specific: perhaps a different path to your database in prod vs development, or instructions for your IDE that may not be to the taste of someone else working on the project with the same IDE.
- boring_twenties 6y agoset -o noclobber