> - ~/.config/foo -- only you write files here, so it's your detritus, not the program's :)
That's not true.
> ls ~/.config/cef_user_data/Dictionaries
> en-US-9-0.bdic
That's a dictionary file written in a binary format. I don't even know what program wrote this crap there, only that it's embedding chrome (CEF).
> ls ~/.config/ibus/bus/
> dcf58003d1744e71aa86dd97e951d49d-unix-0 dcf58003d1744e71aa86dd97e951d49d-unix-1 dcf58003d1744e71aa86dd97e951d49d-unix-wayland-0
Files describing how to do IPC with current processes. They belong to ~/.local/state not .config.
This time, I won't even try to make a judgement as to what is "my detritus" as opposed to the program's because there are too many files involved, and will just show how much they occupy on my drive despite being in .config when 90% of them really ought to be in .local/share and .cache
> cd ~/.config/google-chrome
> du -h
> 999M .
Ahem. I think the idealism toward the XDG spec has not panned out.
By the way, Chrome does have folders in .cache :
> cd ~/.cache/google-chrome
> du -h
> 651M .
But, I believe it doesn't put "local storage" stuff from webapps there.
It doesn't use ~/.local at all.
~/.config is broken beyond belief and not the place where you just have "your config files".
The only sane way to manage "your config files" is to put them in a git managed folder and use a symlink farm program.
That's not true.
> ls ~/.config/cef_user_data/Dictionaries
> en-US-9-0.bdic
That's a dictionary file written in a binary format. I don't even know what program wrote this crap there, only that it's embedding chrome (CEF).
> ls ~/.config/ibus/bus/
> dcf58003d1744e71aa86dd97e951d49d-unix-0 dcf58003d1744e71aa86dd97e951d49d-unix-1 dcf58003d1744e71aa86dd97e951d49d-unix-wayland-0
Files describing how to do IPC with current processes. They belong to ~/.local/state not .config.
This time, I won't even try to make a judgement as to what is "my detritus" as opposed to the program's because there are too many files involved, and will just show how much they occupy on my drive despite being in .config when 90% of them really ought to be in .local/share and .cache
> cd ~/.config/google-chrome
> du -h
> 999M .
Ahem. I think the idealism toward the XDG spec has not panned out.
By the way, Chrome does have folders in .cache :
> cd ~/.cache/google-chrome
> du -h
> 651M .
But, I believe it doesn't put "local storage" stuff from webapps there.
It doesn't use ~/.local at all.
~/.config is broken beyond belief and not the place where you just have "your config files".
The only sane way to manage "your config files" is to put them in a git managed folder and use a symlink farm program.