• @Delta_V@lemmy.world
    link
    fedilink
    222 months ago

    not seen in this comic: the linux file isn’t where the comic/manual/internet nerds says it should be, and there’s no realistic way to find it

    • dream_weasel
      link
      fedilink
      32 months ago

      Sure there is: find / -name myprogram*.md -o -name myprogram*.txt or start with just looking for the program name and pipe to less

        • dream_weasel
          link
          fedilink
          52 months ago

          The prompt was realistic not simple lol. Usually some man or programname -h and then reading will tell you where to look and that’s simple. Not many people want to hear “RTFM” though.

    • @baseless_discourse@mander.xyz
      link
      fedilink
      1
      edit-2
      2 months ago

      Until flatpak came along and just keeps everything in their respective app sandbox.

      If your app don’t need full user home access (most app don’t), you can use a persistent folder to place the folder in app sandbox instead of home.

      It is not only more clean, but also more secure and private.

    • @ricdeh@lemm.ee
      link
      fedilink
      -12 months ago

      Nonsense. And even if the config file cannot be found in the usual directories then there are always tools like KFind that can search your entire OS within seconds.

      • @Delta_V@lemmy.world
        link
        fedilink
        102 months ago

        congratulations. you’ve just sent a linux newb down a 12 hour rabbit hole that doesn’t actually solve their problem.

        • @ricdeh@lemm.ee
          link
          fedilink
          22 months ago

          How does it not solve their problem if they’re searching for configuration files? That would only be the case if the files do not exist in the first place, and then there’s really no difference between GNU/Linux and Windows at all if you assume that initial configuration has not occurred. What would you do?