No, one directory you need to backup for when things go sideways, and the other can go to /nev/dull.

This is why so many people have a separate git repository for their config files and a scripts that symlinks or copies those files into the actual ~/.config.

Archwiki has a huge list of apps that do this with instructions on how to force them to not do this. You might find it useful.

Personally though, I’ve given up on wrangling stubborn apps and just use flatpak and docker for everything. It can’t crap in your ~/ if it doesn’t have access to it!

XDG_DIR, Portals, Secrets, D-Bus, the Desktop file spec, Appstream… are there for you to read. 🥰

Standard compliance is a total mess in the world of linux desktop apps. My pet peeve is that $XDG_RUNTIME_DIR should point to a customizeable tmpfs that apps can use to store temporary data. But just TRY setting to anything else besides /run/user/1000 lol. Half your apps will be broken. Even apps that are made by/for the freedesktop people (e.g. Helvum, the pipewire patchbay app) struggle with this lol. This spec came out in 2021 – three years ago – and it’s already ossified to the point of being barely useful. At this point I don’t blame devs who say “fuck it” and just dump their tempfiles into /tmp the way god dennis ritchie intended.

Huh, TIL

~ $ /bin/true --help
Usage: /bin/true [ignored command line arguments]
  or:  /bin/true OPTION
Exit with a status code indicating success.

      --help        display this help and exit
      --version     output version information and exit

NOTE: your shell may have its own version of true, which usually supersedes
the version described here.  Please refer to your shell's documentation
for details about the options it supports.

GNU coreutils online help: <https://www.gnu.org/software/coreutils/>
Full documentation <https://www.gnu.org/software/coreutils/true>
or available locally via: info '(coreutils) true invocation'

I honestly don’t know what I prefer more, the overengineered GNU true, or the true that shipped with some older system that was literally just an empty file with the executable bit set.

This is such a stupid take. Gui obscures the thing that you want to do behind endless buttons and menus and some bullshit that some self-proclaimed “user experience engineer” thought would be “intuitive”. With cli it’s like you’re talking directly to the computer. Want to stop the networking service? service networking stop. Couldn’t be simpler!

Also fun fact, Linux has a “wireless devices” tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can’t make a permanent setting.

Are you talking about rfkill? Strange, for me the ID’s don’t change. But even if they do for you, what’s stopping you from getting the ID just by grepping for the device name? Something like rfkill list | grep YOUR_DEVICE_NAME | cut -d ':' -f 1 | xargs rfkill block.