vitor

Locking this thread to avoid splitting the conversation. If you want to request more Workflows, please do so on the following thread: But remember this does not preclude you from informing the developer that their Workflow has stopped working. It’s better for everyone if they’re informed sooner rather than later.

Added.

All of them have been added. But do note: There are alternatives to that one, including my own SynAnt which is still maintained but uses a different API. That one is by @deanishe, who is a prolific Workflow author. No problem with asking for the stopgap, especially since the last released version of the Workflow was years ago and doesn’t include a required library update, but do note you shouldn’t skip on asking the authors about updates for the Workflows you care about, it’s possible they are already working on it or don’t yet know of the Python deprecation. I’m certain Dean knows, but the following developer may not: That developer was active on the GitHub repository a month ago so you may wish to let them know of the Python issue there or on the forum thread.

@Luca That is also covered in the instructions. Change google_drive_path. Making it /Volumes/GoogleDrive/ should be enough

Correct. It hasn’t been maintained for a while despite staying up. The official place to share Workflows is this forum. Nonetheless, the effect of Packal was large enough that it continues to be used and get submissions, despite features breaking.

@jmonda Have you read the page I linked you to? The Workflows you want are right there and already fixed.

Open Alfred: osascript -e 'tell application id "com.runningwithcrayons.Alfred" to search' Open and search for something specific: osascript -e 'tell application id "com.runningwithcrayons.Alfred" to search "something specific"' To hide it, simulate esc: osascript -e 'tell application "System Events" to key code 53'

For people already on the Monterey beta, if you’ve followed the knowledge base article to reinstall Python 2, this version should work. It modifies the Workflow just enough for it to work with the newly installed Python 2. @dfay may be interested in updating this for Python 3 or another language, so consider the above a stop gap if you’re in a hurry. If the Workflow has any kind of auto-update, the linked modified version will respect it.

Once Monterey 12.3 is released, this will break unless it’s updated before then. For people already on the beta, if you’ve followed the knowledge base article to reinstall Python 2, this version should work. It modifies the Workflow just enough for it to work with the newly installed Python 2. If we get an official update in the meantime, so much the better. If the Workflow has any kind of auto-update, the linked modified version will respect it.

Developers aren’t going to make new Workflows in Python 2. That would defeat the purpose because the only point of using it was that it was bundled with macOS. The ones mentioned in this thread: percent change, case converter, and power thesaurus are simple fixes (check the bottom of the page). For searching unicode symbols, I’m not entirely sure which one you’re referring to but there are a handful of Workflows that do that and not all require Python 2, so you may wish to try an alternative. Please provide links to the original posts when making requests.

If you’ve followed the knowledge base article to reinstall Python 2, this version should work for you. It modifies the Workflow just enough for it to work with the newly installed Python 2.

With macOS Monterey 12.3, Apple removed the bundled Python 2 interpreter. That means older Workflows dependent on Python 2 will no longer work without modification. You can reinstall Python 2, but some Workflows will still require a tweak to work. It’s simple enough to do if you know what to look for, but not everyone does. The Updated Third-Party Python 2 Workflows repository on GitHub is meant to close that gap. Check the list of available Workflows. If the one you need isn’t present, ask for it there or as a reply on this thread. Be sure to include a link to the original. Note this is only for Python 2 Workflows which break on Monterey 12.3 and above due to the Python 2 removal. If a Workflow stops working for any other reason, contact the author as usual.

It is not. Alfred works that way by design. Imagine the case where you had one (or multiple!) slow Workflows all trying to shove their results in the regular search. It would be a mess.

Hadn’t heard of it. But in addition to being a GUI app (which I don’t want), it’s clearly abandoned: the repo starts with “Syncalicious is in its early stages of development” and the last commit was two years ago. In contrast, Tape is probably done. If it works—and for me it does—the core tool probably won’t get many updates, just the definitions.

@deanishe @nikivi In case you’re still interested, I finally released my mackup alternative; you’re the first to know. The current list of supported apps is a tad weird, some of them may even be discontinued. I’m not particularly enthused about the problem space of backing up app settings, I just wanted something fairly robust for my needs and it didn’t exit. I’ve been hackilly and manually using snippets of this code over the years and it has worked well, but because it’s only needed on occasion I had been indefinitely putting off making it into a proper tool. I’ll probably expand the list of supported software, but that’s hand waved into the future. I take PRs, the format is dead-simple.

This is purely observational, but for a while now every time I see a new Python Workflow submitted to the forum it requires Python 3.

@Tekl That wouldn’t work. You can’t guarantee a Python 2 script works with Python 3, that’s why the transition was such a mess. Plus, if those developers used External Scripts themselves, the dropdown doesn’t matter. Right now what you want is to recover Python 2. Alfred will pick that up, just like it does with PHP.

Probably best to teach you to do each individually, so you can connect them later. To create a new folder, make a Run Script Action with default settings and code: mkdir -p "/full/path" Use ${1} to insert a previous argument. For example, if you used a Keyword Input and gave it an argument of New Render Collection, then the following code: mkdir -p "/Volumes/Chronos Access/${1}" Would create /Volumes/Chronos Access/New Render Collection. To link to a file or folder, use the same setup and code: ln -s "/full/original/path" "/full/target/path" Example: ln -s "/Applications/Safari.app" "/Volumes/Chronos Access/Safari" ${1} also works. To create a file link a website, use a Write File Output. Save the filename with a .webloc extension, and in the contents: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>URL</key> <string>https://www.alfredforum.com</string> </dict> </plist> Note the https://www.alfredforum.com, which you need to change to the desired result. In this case, use {query} or {var:varname} to make it dynamic. The bottom of that window and the linked documentation explain that part.

Technically, for this specific case, just installing the Developer Tools is enough because they ship Python 3. If you use External Script to a script with the right shebang or /bin/bash calling /usr/bin/python3, you get that GUI prompt and Python 3 is installed. Because Homebrew requires the Developer Tools, just installing Homebrew and doing nothing else already guarantees a Python 3 version. It’s a version from 2019, though; don’t assume Apple will keep it up with the times. @Chris Messina is right. A Python from Homebrew is preferable, and because that cannot be guaranteed to exist on a user’s computer it wouldn’t work to simply list it in the dropdown without something extra.

Remove the space from the end.

Indeed, it is not. Alfred just tells macOS “hey, open this URL” and then macOS decides how to do it. It probably is consistent, but has nothing to do with which one is in the foreground. It’s bound to be either the oldest or newest window. Because in that situation the browser isn’t asking macOS to open the link, it just does it. Since both actions (the request to open and the opening) happen in the same app, it has complete control over the behaviour. Again, not possible because Alfred is just telling macOS to open the URL. You can do it with a Workflow, but you have to remake the web searches and the browser you’re using matters because that’s the crux of the problem: you need to tell that app specifically to open a new window.

@Will422 That is covered in the instructions. Edit google_drive_path to /Volumes/GoogleDrive.

I doubt that’s possible. I have never seen a tool which changes the system volume and shows that indicator. If you find a command-line utility or command which does it, we can help you integrate it.

There you go. The trick is to first save it as a file then read it as image data into the clipboard. One could also do the reverse. I don’t know what you’re asking there.

Open Alfred and press the up arrow on your keyboard.