(#yfko2ya) I wonder if I should regularly wipe `XDG_STATE_HOME` just like I do with `XDG_CACHE_HOME`. So far, only wireplumber appears in this directory … Hm …

(#yfko2ya) @movq My `XDG_STATE_HOME` directory doesn't even exist, no program has created it. > $XDG_STATE_HOME defines the base directory relative to which user-specific state files should be stored. If $XDG_STATE_HOME is either not set or empty, a default equal to $HOME/.local/state should be used. > > The $XDG_STATE_HOME contains state data that should persist between (application) restarts, but >that is not important or portable enough to the user that it should be stored in $XDG_DATA_HOME. It may contain: > > actions history (logs, history, recently used files, …) > > current state of the application that can be reused on a restart (view, layout, open files, undo history, …) I don't believe it's a good idea to wipe it. $ cat /etc/fstab ... swap /home/adi/var/cache mfs rw,-s512M,noatime,nosuid,nodev 1 0 and for `XDG_CACHE_HOME`.

(#yfko2ya) Related threads

(#yfko2ya) @adi So how do your other XDG variables lool like?

(#yfko2ya) @adi Huh, you're right. I never thought about that.

(#yfko2ya) @adi > I don't believe it's a good idea to wipe it. Hmm, that list sounds just like the sort of thing that I'd want wiped. 😅 Probably a matter of personal taste. By “wiping”, I mean mounting it as tmpfs / mfs. (Deleting that directory during runtime is probably a very bad idea, yeah.)

(#yfko2ya) @lyse export XDG_DATA_HOME=~/share export XDG_CONFIG_HOME=~/etc export XDG_STATE_HOME=~/local/state export XDG_CACHE_HOME=~/var/cache export XDG_RUNTIME_DIR=~/var/run

I wonder why people didn't settle on `XDG_CONFIG_HOME` as `~/etc`. Makes so much sense!

(#yfko2ya) @adi Ah, didn't know about the "recently" added state directory.

(#yfko2ya) @movq I so wouldn't want to delete this : > view, layout