Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Infat – Declaritive application assocation manager for macOS

github.com

Post reply on HN
Print view View original

1–10 of 43 posts

Show HN: Infat – Declaritive application assocation manager for macOS

#1

Post by philocalyst »

Bello! Made this to help navigate the tumultuous process of navigating to a new machine on Mac when you have a number of custom utilities setup for editing particular files. This is designed to make that as easy as possible, and add some magic on top of that, like setting mailto handlers or anything else of that breed. Use XDG_CONFIG_HOME to keep it organized.

Credit to https://github.com/moretension/duti for the original inspiration for the project.

Happy to answer and help with whatever.

Show HN: Infat – Declaritive application assocation manager for macOS
github.com

Re: Show HN: Infat – Declaritive application assocation manager for macOS

#5

Post by philocalyst »

mlenz wrote: post #3

Great to see this, thanks for sharing! Do you have plans to make it available in nixpkgs and potentially as a home-manager or nix-darwin module? Then I could add it to my config and have everything set up automatically.

I don't use nixpkgs personally but would love to give it a shot, check the repo in a day or two to give me some time to learn to ropes! I'll shoot you an email if I need any help :)

Re: Show HN: Infat – Declaritive application assocation manager for macOS

#7

Post by philocalyst »

deeThrow94 wrote: post #2

Oh this is very exciting! I do have a request, though—I want to list all file extensions an application can open, specifically so I can use this to ensure xcode isn't the default for anything but xcode-specific files.

Have an idea of how I would do this already, give me until the end of the week. To be clear, an interface like this?

Infat list [--identifier] [--application] Where identifier and application are mutually exclusive, and application lists the openers it is capable of opening by default? Merging the application flag for simplicities sake, so either returns a list with both their possibilities *and* the assigned apps.

Thoughts?

Re: Show HN: Infat – Declaritive application assocation manager for macOS

#8

Post by deeThrow94 »

philocalyst wrote: post #7
deeThrow94 wrote: post #2

Oh this is very exciting! I do have a request, though—I want to list all file extensions an application can open, specifically so I can use this to ensure xcode isn't the default for anything but xcode-specific files.

Have an idea of how I would do this already, give me until the end of the week. To be clear, an interface like this? Infat list [--identifier] [--application] Where identifier and application are mutually exclusive, and application lists the openers it is capable of opening by default? Merging the application flag for simplicities sake, so either returns a list with both their possibilities *and* the assigned apps. T…

Love it! Seems like it'd be easy to filter out extensions I wanna keep and switch them all to emacs or whatever.

Re: Show HN: Infat – Declaritive application assocation manager for macOS

#9

Post by stinger »

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.

Re: Show HN: Infat – Declaritive application assocation manager for macOS

#10

Post by philocalyst »

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 :(

Post reply on HN