I wholeheartedly agree with this blog post. I believe someone on here yesterday was asking about config file locations and setting them manually. This is in the same vein. I can’t tell you how many times a command line method for discovering the location of a config file would have saved me 30 minutes of googling.

  • I_Miss_Daniel
    8•1 year ago

    (Windows) Resource Monitor, disk tab, tick the process, see what files it opens and closes.

    Also the usual %programdata% and the two %appdata% find most things.

    • exscape
      4•1 year ago

      Do things stay in that list when they are not used (since they would be opened and closed in far less than a second)? If so that’s pretty cool.

      If not, you can use Process Monitor to check this. That’s what I usually do.

    • bionade24
      3•1 year ago

      The *nix equivalent is the lsof command. This doesn’t help you finding out in which hierarchy config files are parsed when the program accesses multiple ones, which is often the case.

      • elmicha
        10•1 year ago

        You can use something like strace -eopen -f -o strace.out the_program to find all files that the program tried or succeeded to open. Then you can try to find the config file(s) in strace.out.

        • bionade24
          2•1 year ago

          You still don’t know which location is preffered and how get they get merged. In my experience, digging into the source is the most straighforward. But my usual problem is more that the config option doesn’t do at all what the documentation says it does.

            • @Hexorg@beehaw.org
              1•1 year ago

              Yes, though if two different files allow for the same config key - you’re stuck opening both to check

              • bionade24
                1•1 year ago

                And you still couldn’t be sure, could be parsed the other way around for historic reasons.
                Just reading the source code (if possible ofc) is imho easier than reading.