Infat, a new command-line tool for macOS, is gaining attention for its ability to declaratively manage file-type and URL-scheme associations. The community has responded positively to this utility that simplifies the often tedious process of setting default applications for various file types and URL schemes.
Key Features of Infat
- List which apps open for specific file extensions or URL schemes
- Set default applications for file extensions or URL schemes
- Load associations from TOML configuration files
- Designed for scriptability and automation
- macOS-native using NSWorkspace, Launch Services, and UTType
- Available via Homebrew:
brew install philocalyst/tap/infat - Open source under MIT License
Nixpkgs Integration on the Horizon
Users have expressed interest in seeing Infat available through additional package managers, particularly Nixpkgs. The developer has shown enthusiasm about this possibility, stating they plan to learn the necessary steps to make it available as a home-manager or nix-darwin module. This would allow users to automatically configure their file associations as part of their broader system configuration, further streamlining the setup process when moving to a new machine.
Handling Text Files Without Extensions
A notable feature request emerging from community discussions involves the ability to set default applications for entire categories of files rather than just specific extensions. One user specifically asked about configuring all text-like documents, including those without extensions, to open with a single editor. The developer has responded positively, suggesting they could implement a new type configuration option within a week that would allow users to define openers for categories of files such as text or video.
Clarification on Functionality
Some users sought clarification about exactly what the tool does. The developer confirmed that Infat allows users to specify which application opens when clicking on a file via Finder or when using the terminal's open program. This functionality addresses a common pain point for Mac users who frequently need to reconfigure their default applications, especially when setting up new machines.
Troubleshooting Installation and Usage Issues
The community discussion has revealed some implementation challenges. One user reported errors when trying to set default applications for extensions they hadn't previously opened on their system. The developer has requested more detailed information with verbose logging enabled to investigate this issue.
Another point of confusion involved the installation process, particularly the dependency on just, a command runner that serves as an alternative to Make. The developer clarified that while just is used to organize the build process, users can alternatively install Infat via Homebrew or build directly with Swift Package Manager.
Future Feature Development
Looking ahead, the developer appears responsive to feature requests. One user asked for the ability to list all file extensions an application can open, specifically to prevent Xcode from being the default for non-Xcode files. The developer has committed to implementing this functionality, proposing an interface that would allow users to see which file types an application can open and which ones are currently assigned to it.
The community's reception to Infat highlights the ongoing need for better tools to manage system configurations on macOS. As one user commented, swapping machines on Mac is usually a pain, suggesting that declarative configuration tools like Infat could significantly improve the user experience when setting up new systems or maintaining consistent environments across multiple devices.
With the developer's apparent commitment to implementing community requests and fixing reported issues, Infat seems positioned to become an increasingly valuable utility for macOS power users and system administrators looking to automate their workflow configurations.
Reference: Welcome to Infat