Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add extension to UTI? #9

Open
balthisar opened this issue Dec 29, 2014 · 0 comments
Open

Add extension to UTI? #9

balthisar opened this issue Dec 29, 2014 · 0 comments

Comments

@balthisar
Copy link

*duti is probably working as designed; I was hoping it would allow me to assign an extension to an existing UTI.

For example currently I have a lot of source files -- say, .haml -- that have a dynamic UTI (mdls reports kMDItemContentType = "dyn.ah62d4rv4ge80u2prru"). The ContentTypeTree, naturally, doesn't contain an appropriate content type, and Mac OS X (Yosemite, but same problem existed on earlier systems) doesn't even recognize that .haml is an extension.

All I want to do is tell Mac OS X that .haml (and other extensions) is, in fact, an extension, and that the extension refers to public.plain-text (or whatever else I want to point it to).

I'm fairly certain I could make a dummy Mac OS app in Xcode with CFBundleTypeExtensions to make all of these associations, but these seems stupid if LaunchServices is simply going to copy them from the plist anyway.

tl;dr: Is this some type of functionality that would be possible to add to duti? E.g., extension .xxx means UTI com.something.whatever.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant