Technology

37801 readers

220 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

792

All programs should tell you where they store config files (utcc.utoronto.ca)

submitted 2 years ago by wet_lettuce@beehaw.org to c/technology@beehaw.org

97 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] leirda@lemm.ee 2 points 2 years ago

You can call it recursively on .config (for instance), and watch for specific events (creation, deletion, modification, etc). But I expect this to be expensive on really large folders and I'd avoid it if I could.

Btw it's syscalls iirc (inotify-tools just exposes them)