Bahman M. (@bahmanm@mastodon.social)
mastodon.social
Attached: 1 image My fellow software engineer, It's the year 2024. Please store your #Linux #desktop application configurations ONLY in `$XDG_CONFIG_HOME`. NOT in `$HOME` or other non-standard or obsolete places. May #FreeDesktop be your guide. https://www.freedesktop.org/wiki/Specifications/ #Programming #DevOps #SysAdmin

Shameless plug: I am the author.

    • Eager Eagle@lemmy.worldEnglish
      4·
      2 years ago

      off the shelf go was too annoying for me

      Nowadays I set GOENV_ROOT to an XDG location and use goenv instead.

  • Wispy2891@lemmy.world
    27·
    2 years ago

    100% agree and I also despise devs who do this on windows, instead of using %appdata% they’re using c:\users\username\.myappisimportantandtotallydeservesthisdir

    • Tlaloc_Temporal@lemmy.ca
      1·
      2 years ago

      To be fair here, appdata is technically a hidden folder and there are lots of reasons an app would want it’s data accessable by the user.

      • Wispy2891@lemmy.world
        4·
        2 years ago

        Yes but then just spam the documents folder like anyone else, don’t hoard the home root for no reason except that is a lazy cross platform port

  • MonkderDritte@feddit.de
    14·
    2 years ago

    Where did i read this… basically, the .file being hidden being a bug in the early unix filesystem, which got misused to hide configuration files.

    Offenders despite XDG-variables set and with no workaround:

    • .android: hardcoded in adb and i guess something in mtp too
    • .pki: some tool/library Firefox and Chromium sometimes use.
    • .steam: yes, that

    Btw, https://wiki.archlinux.org/title/XDG_Base_Directory

  • dohpaz42@lemmy.worldEnglish
    10·
    2 years ago

    Here is a more concise way to achieve the same thing:

    ls -ACd ~/.??*/ | sed -e "s#$HOME/##g"
    • Samueru@lemmy.ml
      2·
      2 years ago

      ls -A | grep "^\."

      I had to make a dummy .dotfile to test because I don’t have hidden files in my home.

    • dizzy@lemmy.ml
      3·
      2 years ago

      Whoa I’m a stickler for getting as much as I can out but even I have .zshenv and some other too hard to figure out things in there. How’d you manage a total wipeout?

      • Samueru@lemmy.ml
        2·
        2 years ago

        zsh is actually easy and it is detailed in the archwiki

        You have to set $ZDOTDIR in /etc/zsh/zshenv and iirc that was the only location that required root to edit.

        For the rest of stuff, here is how I fix steam for example and you can check the rest of my dotfiles for how I configured zsh and all of that.

        Although I haven’t updated them, I still had a .local directory back then, it was 1 week ago that I changed .local for Local and that let to an issue with distrobox which I made a PR fixing it that’s still open though.

      • Samueru@lemmy.ml
        1·
        2 years ago

        It’s empty lol, it’s a directory on tmpfs that i use to build programs and similar stuff to not be hammering my ssd with unnecessary writes.

        I have $XDG_CACHE_HOME in tmp as well and I moved the mesa sharer caches to $XDG_STATE_HOME as that’s really the only thing so far I’ve needed to preserve.

        • tabular@lemmy.worldEnglish
          1·
          2 years ago

          tmpfs (…) to build programs (…) to not be hammering my ssd with unnecessary writes

          Sounds useful. How did you setup the directory?

          Running df tells me “tmpfs” is mounted on /run. If I build in that that directory then would it be stored in RAM, or do I need to do something else?

          • Samueru@lemmy.ml
            3·
            2 years ago

            I have /tmp in my fstab with these mount options.

            tmpfs /tmp tmpfs rw,noatime,size=20G 0 0

            And the rest of the setup is done in my zprofile

            • tabular@lemmy.worldEnglish
              2·
              2 years ago

              I think I should be able to get this working following your zprofile file. Thanks!

  • Mactan@lemmy.ml
    61·
    2 years ago

    there’s no place like 127.0.0.1

    there’s no place like XDG_CONFIG_HOME.

  • wvstolzing@lemmy.ml
    3·
    2 years ago

    vim now has an option to put the .vim folder in ~/.config; though I’m not sure if the default plugin/package & syntax folders can be set under ~/.local/share.

  • davel [he/him]@lemmy.mlEnglish
    510·
    2 years ago

    This would just further complicate things for me. It assumes that 1) the system even has a windowing system/desktop environment or 2) all the installed software is XDG-aware. Most of the time I’m fiddling with headless environments.

    • Eager Eagle@lemmy.worldEnglish
      8·
      2 years ago

      The spec doesn’t make those assumptions at all, idk where that’s coming from.

      I have headless machines with XDG vars configured and ones without them. XDG compliant software works in either case, but I’m less likely to use a piece of software that clutters my $HOME.

  • GolfNovemberUniform@lemmy.ml
    316·
    2 years ago

    But what’s the difference? It’ll be in /home anyways and I heard BSD had some issues with something that could be XDG.

    • mrvictory1@lemmy.world
      15·
      2 years ago

      Better organization and backup / restore. For example if you want to restore config files but don’t want to move over the large “.local” folder, applications that write to $HOME will create diifculty.

    • just_another_person@lemmy.world
      10·
      2 years ago

      Because, like /etc, you know there is a designated place for config files. It’s already set for you right there, and there is a standard for it.