pixelgeek Posted March 2 Share Posted March 2 A Workflow to read the UTIs associated with a particular file type. Read me and details are in the repository https://github.com/lolbat/Alfred-Workflow-Read-UTI It is a small tool to help fix a very unlikely problem that is detailed in this thread. It uses a Keyword input and then takes a single file extension. Data is copied to the clipboard. Inspired by @Stephen_C's similar Workflow Link to comment Share on other sites More sharing options...
vitor Posted March 2 Share Posted March 2 (edited) Thank you @pixelgeek, this can go in shortly. I see one quick possible improvement: if we type a “wrong” extension (e.g: .wqedsa) nothing is copied but we still see the notification. Two quick ways to solve that: Tick the Only show if input has content box in the notification, so it won’t show in those cases. Use a conditional and show different notifications. Perhaps even an error sound! Like so. Edited March 2 by vitor Fixed link Link to comment Share on other sites More sharing options...
pixelgeek Posted March 2 Author Share Posted March 2 I'll add some error checking. BTW the link you posted just generates an error. Link to comment Share on other sites More sharing options...
vitor Posted March 2 Share Posted March 2 17 minutes ago, pixelgeek said: BTW the link you posted just generates an error. Fixed! Link to comment Share on other sites More sharing options...
pixelgeek Posted March 2 Author Share Posted March 2 I added a check to make sure there was data being sent and I also checked to make sure that the user added a '.' to the extension they entered https://github.com/lolbat/Alfred-Workflow-Read-UTI Link to comment Share on other sites More sharing options...
vitor Posted March 2 Share Posted March 2 (edited) Thank you. Live now at https://alfred.app/workflows/lolbat/read-uti-data/. 15 minutes ago, pixelgeek said: also checked to make sure that the user added a '.' to the extension they entered Might not be necessary. In the previous version I tested, entering an extension without the . also worked. Quick question: I see that in the previous release you attached the workflow, but in this one you did not but included the workflow in the repo. Which method will you use going forward? Attaching to releases is preferred, but either is OK. I just need to know to implement how to check for updates. I like your organisation, I think @Stephen_C might enjoy checking it too. And the sound you picked made me laugh! Does it ship somewhere with macOS or did you get it from somewhere else? Edited March 2 by vitor Link to comment Share on other sites More sharing options...
pixelgeek Posted March 2 Author Share Posted March 2 10 minutes ago, vitor said: Which method will you use going forward? Which do you prefer? I don't really have any preference. Whichever makes your work easier. 11 minutes ago, vitor said: And the sound you picked made me laugh! Does it ship somewhere with macOS or did you get it from somewhere else? It is from the Alfred Labs sound pack. 11 minutes ago, vitor said: In the previous version I tested, entering an extension without the . also worked. I'll remove it when I do the next update. Link to comment Share on other sites More sharing options...
vitor Posted March 2 Share Posted March 2 21 minutes ago, pixelgeek said: Which do you prefer? Making releases and attaching there, please. There’s no need to do one on purpose now, it can just be from the next one. By appending .atom to the releases URL one can get a feed of new releases which is generated automatically. That is also possible to do with individual files in repos but is more cumbersome as it depends on them all remaining in the exact same location with the exact same name. Link to comment Share on other sites More sharing options...
Stephen_C Posted March 2 Share Posted March 2 2 hours ago, vitor said: I like your organisation, I think @Stephen_C might enjoy checking it too. @pixelgeek I did as Vitor suggested. It's a really well, elegantly set out workflow of the kind I much appreciate: well done! It almost (but not yet, quite) tempts me to break the habit of a lifetime and install a workflow that has an external dependency. 😀 Stephen pixelgeek 1 Link to comment Share on other sites More sharing options...
pixelgeek Posted March 3 Author Share Posted March 3 3 hours ago, Stephen_C said: It's a really well, elegantly set out workflow of the kind I much appreciate: well done! Thanks. 3 hours ago, Stephen_C said: It almost (but not yet, quite) tempts me to break the habit of a lifetime and install a workflow that has an external dependency. The sound or the command line app? Link to comment Share on other sites More sharing options...
Stephen_C Posted March 3 Share Posted March 3 5 hours ago, pixelgeek said: The sound or the command line app? The command line app. However, I've bitten the bullet, decided to make an exception for your worklfow 😀 and tried to install duti. Sadly, I'm constantly getting an error from the Gallery Dependency Manager "The installer script exited with an error”. I initially suspected it was because I did not have the xcode command line tools installed but I do now and it's made no difference. I still obtain that error after being prompted to install duti. I've seen something about this in the forum previously but, frankly, the forum's search utility makes it a challenge to find it again so, for the moment, I'm stuck. By the way, I appreciate this is not a problem with your workflow but something to do with my setup. Stephen Link to comment Share on other sites More sharing options...
vitor Posted March 3 Share Posted March 3 @Stephen_C When you get an error, you should be getting a specific one. Could you first reboot then try again and screen record it? Please DM with it since I may need to ask for specific info. Link to comment Share on other sites More sharing options...
Stephen_C Posted March 3 Share Posted March 3 This is resolved. For the benefit of others who may wonder how/why/what… I'd recently bought a new M2 Mac and had migrated everything to it from my old Intel Mac. That clearly left Homebrew in the wrong location for an Apple Silicon Mac and (with @vitor's usual invaluable help) reinstalling Homebrew fixed the problem. As a result, @pixelgeek, your workflow is very neat and works well. Stephen Link to comment Share on other sites More sharing options...
pixelgeek Posted March 3 Author Share Posted March 3 Yay! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now