vitor

You mean the Terminal opens but does not show any window?

Yes. Alfred 5 doesn’t break compatibility with older Workflows. There might be a couple of cases where a tweak is needed (e.g. new functionality added to an old object), but it won’t be big. Can you share the file’s contents?

Fixed Workflow, with annotations. Do ask if anything is unclear. Screenshot for object reference:

That sounds a bit too specific for a new GUI option and the expected behaviour won’t be obvious (e.g. JavaScript also has an optional limit on split but it discards the extras instead of mashing them together). Because you already know about Python’s split, it’s easy to replicate it with a Run Script Action. Create one with language set to /usr/bin/python3 and leave the rest as the default. In the code: import sys import json separated = sys.argv[1].split(",", 1) json_object = { "alfredworkflow": { "arg": separated } } print(json.dumps(json_object)) Save it as a prefab and you’re good to go to reuse it whenever you need. You only have to change the split part of line 4, everything else remains the same. This works because you can pass a JSON between Alfred objects to modify them or send additional information. In this case, you’re just passing the arguments already split as you want.

It should show both. Select the correct one two or three times in a row and Alfred will prioritise it.

This should work. You’ll need the latest Alfred pre-release. Take a look at the code in the Run Script, and see how much smaller it can be and remain readable. You’ll notice I changed it to with input as argv, meaning sys.argv[1] instead of {query}. That will save you having to escape things and is in general better (hence why it’s the default).

One more: for file in "${@}"; do open -Wa "/Applications/•Verif Photos/300 RVB.app" "${file}" done It’s weird that Photoshop droplets only accept one file when given arguments directly from the command-line. What we’re doing above is looping through each image and giving them as the argument one at a time. In the new iteration, it will wait for the droplet to exit before going to the next one.

Connect a Fallback Search Trigger to an Argument and Variables Utility with {clipboard} as the Argument. That then connects to your Replace Utility.

You will only if you want to do it to multiple images at once. https://github.com/alfredapp/automation-tasks/issues/1#issuecomment-1169951134

You can get text with a Universal Action Trigger. That’s exactly what it’s for, you just remember one shortcut and have all actions available. You can also get text with a Keyword by connecting it to a Dispatch Key Combo Output with ⌘C, followed by a short Delay (0.1s should work) and a Argument and Variables Utility to send {clipboard}. The Universal Action is the most convenient of the two. Other than the options available, not really seeing what else could be there.

Welcome @anonymousaga, Alfred 1 is not on (any official tap of) Homebrew Cask. alfred always points to the most recent stable version. That is true of any cask in the main tap—the one without a version number is the most recent stable one.

None of this is hidden: if you explore Alfred’s preferences you’ll see everything is organised in logical places with open and readable formats. It allows for other advanced stuff, like accessing clipboard history inside a Workflow. It works pretty well because Alfred is quite fast and stable, but you’re still editing a file in a way it wasn’t intended to. In other words: it works but should still be considered a hack and not an officially supported method, which is why it isn’t officially documented.

When you’re in the Universal Actions pane, drill down to a directory by pressing ⌘↓. You can also make it work with the left and right arrow keys (without ⌘) in Alfred Preferences → Features → File Search → Navigation → Shortcuts. These will also work in the Google Drive Workflow. You do need to know the name of one directory so you can search for it and use it as your “anchor”, but then you go up or down as you please.

It did. It set the directory relative to the automation task itself. You need to give it the full path to the directory to save to. If you need the path to be dynamic, in version 2022.8 of the Automation Tasks (just released, you can update now), I’ve added a Get Path Dirname which will allow you to pass it the path to a file and only get its directory path. You’ll need to make use of the Argument and Variables Utility and Split Argument to save them beforehand and restore as different arguments for the conversion.

Move the folder into ~/Library/Application Support/Alfred/Alfred.alfredpreferences/snippets.

Ah, yes, the droplet is an app. Try: for file in "${@}"; do open -a "/Applications/•Verif Photos/300 RVB.app" "${file}" done

You are! It will be a folder with the name of your collection, containing each of your snippets as JSON files. Assuming the deletion happened recently, sorting your Trash’s contents by Date Added should be a good bet. Yep, macOS does it by default.

It’s common for people to post in the wrong thread or have a tangential problem which needs a different solution. For example, deleting your snippets collection yourself by accident is different than it disappearing without you knowing why. Those issues have different causes and thus different solutions. You asked about syncing with Dropbox but that’s no longer relevant. It would only have helped if you had them synced beforehand. But I can only tell you this after knowing what you were really trying to do. I’m actively trying to help you, but to do that I need your cooperation. Only you have access to your data and the necessary information to figure out what happened. I can give you clues on how to proceed, but only if I understand the details. I just tried to delete a snippet collection and I’m seeing it in the Trash, so the feature is working. If it didn’t in your case, we need to figure out what is different about your setup. I don’t know what you’re referring to in this case.

How did you delete them in the first place? You’re giving information piece meal, but we need as much information as possible to understand your case. It took seven posts to reveal you can’t see your snippets, when that’s the crux of it. Please describe in detail your case and how you got to it.

Can you record your screen while you’re doing the deletion?

Yes, it works for a single Mac too.

What version of Alfred are you on, and where are your preferences stored?

Everything looks correct. Let’s try it another way. Instead of Open File, have a Run Script Action with default settings and the following code: for file in "${@}"; do "/PATH/TO/DROPLET" "${file}" done Replace /PATH/TO/DROPLET with the full path to the droplet.

Welcome @AlfredV, It refers to the macOS Trash Bin. Deleting snippets and workflows sends them there when possible. Syncing Your Alfred Settings Between Macs.

May I see the debugger output?