4 ms·
I find it useful; I might want to version-control .config but definitely not .cache. And if the program is broken I might blow away .cache but not .config.
by kragen 4y ago
I find it useful; I might want to version-control .config but definitely not .cache. And if the program is broken I might blow away .cache but not .config.
- fiddlerwoaroof 4y agoThat still works if it’s `~/.foo/cache`
- Macha 4y agorm -r ~/.foo/cache ~/bar/cache ~/baz/data/app/cache [20 more apps..] is less ergonomic than rm -r ~/.cache/\*
- Macha 4y agoI think HN escaped the * in that final line before I edited it into a code block and my edit window is expired so I can't fix it
- fiddlerwoaroof 4y agoThere’s always: rm -rf ~/.*/cache
- Macha 4y agoAssumes the app uses cache as it's cache, rather than names like dlcontent, bananas_content, storage.sqlite, assets, meta, $TIMESTAMP.txt etc.
- fiddlerwoaroof 4y agoWell, I don’t mind standards, I just prefer all the files an app touches to be under a single root folder (that’s not just $HOME)