Show HN: Infat – Declaritive application assocation manager for macOS

Post by emmelaich » Fri, Apr 25, 2025, 10:58 PM UTC

AdieuToLogic wrote: post #23

goranmoomin wrote: post #21

This is a bit tangent, but does anyone know how to block an app from ever deciding to become a file handler on macOS? Every time I install Chrome on my machine (for testing purposes), macOS decides that Chrome is going to be the default file handler for a bunch of file associations, including HTML, WebP, and so on… and I have to figure out which was which for all of the mappings (which is super frustrating). I can re…

> This is a bit tangent, but does anyone know how to block an app from ever deciding to become a file handler on macOS? The information below does not "block an app" from taking over file handler associations. It may be beneficial on its own and/or provide a starting point for further exploration. > Every time I install Chrome on my machine (for testing purposes), macOS decides that Chrome is going to be the default…

    ~/Library/Preferences/com.apple.LaunchServices/com.apple.LaunchServices.plist

Post by stinger » Mon, Apr 28, 2025, 4:25 PM UTC

philocalyst wrote: post #10

stinger wrote: post #9

Running into this error - "Error: Failed to set default application: The file couldn’t be opened." This seems to be happening for extensions that I haven't opened yet (md, json, mailto, etc.) For a new laptop, this might not be available yet. Once I `touch` a file with those extensions, the config works!. FYI, I am using a config.toml file btw.

Okay, confusing -- just tried to replicate on my machine and couldn't get that error. When you say touch, you mean creating a file with that extension, or any interaction period? Could you please try to replicate with verbosity enabled (-v) and email me the output or file an issue at the repo with the results and full summary? It's helpful for tracking. Sorry this isn't a quick fix :(