Earlier quoted context omitted.
> Same reason why we have a ~/.config folder now instead of just shoving everything into ~/ like we used to. Who/what is the "we" here? Last I checked my homefolder was still chock full of dotfiles in-use.
Now, half of them are in ~/.config This is better because it means you have to look in more places. Similarly, things also like to hide state in ~/.cache If they didn’t then rm -rf .appname would restore it to default settings, and we can’t have that.
The creeping scourge of tooling config files in project root directories
211–214 of 214 posts
Re: The creeping scourge of tooling config files in project root directories
#212I don't get this, what's the problem here? Having config files in root means you know they can apply to all sub directories. This has nice properties like recursive behaviours (see .gitignore) If you want to put (most of) your config files in a .config folder, then most apps should support that If you want to view your config files in a different way, then actually you're trying to solve a different problem. Perhaps…
I agree it wouldn't make sense to put the configs on a global folder like $HOME/.config but I don't see what would be the problem of putting them on a .config folder at the root of the project directory. Recursive behavior would still work, the same way that Git can recognize that there is a ".git" directory in one of the ancestor directories.
With .config folder at root of project then paths in configs are ../whatever/ instead of whatever/ and ../ is evil plus having ../ on front of every path is noisy.
Re: The creeping scourge of tooling config files in project root directories
#213How conscientious. And yup, conventions like this work well Linux and BSD's. To note ~/.config for many configs These days you see this happening inside of .github/, where configs related to gh repos and actions go. If tooling authors started universally recognizing .config/ as a directory where we could keep stuff, the root could be super clean. How about just one file, across languages / CI tools / etc? a "project.…
Windows goes a step further with AppData Local and Remote. Which is a good distinction for those of us who like to sync with roaming folder. Sadly there's a confusing LocalLow and not all apps use AppData anyway. But it's something.
> AppData Local and Remote
I never understood the difference between both. What is it!?
Re: The creeping scourge of tooling config files in project root directories
#214Earlier quoted context omitted.
Windows goes a step further with AppData Local and Remote. Which is a good distinction for those of us who like to sync with roaming folder. Sadly there's a confusing LocalLow and not all apps use AppData anyway. But it's something.
> AppData Local and Remote I never understood the difference between both. What is it!?
I meant 'Roaming' sorry. And IIRC the roaming is for companies that use network storage or sync to keep people's settings no matter what workstation they use.