Which contains comment tokens, block and line, common language servers, special pairs, recognized shebangs, root scopes, etc.
It's mostly for use in one of my other projects, although you can see some of its higher aspirations one day in the README. Would love to collaborate with you and make it useful for a real use-case outside my own! If any of the information contained there could be useful! Reach out through an issue or through an email (linked in my github profile) if you're keen
Walking back my regex commitment, just a heads-up/apology if you had your hopes up. Want this to stay as a CLI and not a dynamic app. Let me know if there's anything else you could see useful that would fit within that scope!
Walking this back, the API only allows setting this up for app bundles, which adds another layer of complexity I'm not down for. I want it to be a CLI tool, it doesn't need a helper or any other layers.
I loveee hammerspoon. And had a subscription to OpenIn a bit back. Advanced scripting isn’t going to happen, even paging out to another script. Recently committed to Regex which would cover most of that. I’ll look into how it “fixes” old associations.
MacOS doesn't give any way to block an association from happening, I'm assuming they're using the same API's under the hood that Duti is using, and the only way you could block that from being accessed is by disabling the Launch services API.
In the next release of Infat, I'm introducing listing the openers from the plist (As you're doing now). If you record these values, then get their set defaults through infat, you could put those into your config and load from you config whenever they're overriden!
There is not, infat is subject to the limitations of Apple's API for setting handlers, which do not support passing in any data that an application could work with. If you wanted to, and have the time, I would recommend setting up a wrapper with https://github.com/sveinbjornt/Platypus with applescript. Then you could make an alternate for whichever mode you please and set it as an opener using infat. Clunky but functional.
It wouldn't be possible with the current interface, but I have a feeling it's possible. I'm thinking it's part of a new configuration option "type" that allows you to define openers for categories of files (text,video,etc.)
No dependencies for install, just is the command runner I use to keep things organized, it's a replacement for make(1). If it hurts to download just, you can build using SPM:
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 :(
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.
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 :)
Love this!! Is there a reason why you chose to not display repository information like the language breakdown or tags? Messing with the sidebar might also be an opportunity to expand the capabilities of the interface, like including a star-chart or LOC.
And there's a number of alternative front-end lists out there that I would submit to if you all are serious about it, and make instructions easy on self-hosting.
Bello! I made this to make the creation and management of licenses on the CLI simple and scalable. Built in Rust (Oooh), full of features, and distributed as a single binary, it's a terrible convenience. Happy to answer any questions/concerns/whatever! First larger project like this and I don't want to stop here in the least. :)))