vitor

It is not. Alfred respects your choices. It depends on what’s causing it to reopen. That’s what we have to find out. Have you installed or updated any Workflow recently? Also, would you mind sharing the names of the files in your ~/Library/LaunchAgents folder? (~ represents your home).

What’s your shell?

Welcome @Karjala, Only you can answer that question, because it’s subjective. The best solution is the one which fits your usage best. That said, I would try #2 first. #1 needs extra setup (which #2 doesn’t), and #2 is by a regular contributor on the forum.

Yes, you did it right. Some redundant steps (no need to uninstall v5), but the end result is what you wanted. Regarding the cause, as per the Onboarding & Migration to Alfred 5 documentation:

Unless there’s another one with the same name that I’m not aware of, that is not possible. DownMedia doesn’t use PHP or any deprecated language. Try brew update-reset and see if that fixes it.

Uploaded the icons where, to what goal? Do you just mean you added them to the Workflow? It’s likely you have a retina screen, so you need to make icons at least twice the size than they will display in for them to look crisp. Alfred’s own icons are drawn with code, they’re not images.

“Optimise Image Colour for Sharing” compresses the image. A Workflow like TinyPNG also does compression, but through an API and with more size reduction. I see the value in these as automation tasks. Most require using external tools (e.g. to convert video you’d use ffmpeg, which does not ship with macOS) so they require a different type of consideration. Thank you for the request.

You’ll notice it’s not quite immediate, it takes a beat and flashes Alfred. A way to achieve the behaviour would be to check if the script input ends in /, and if it does call Alfred via AppleScript with the previous text, which was saved after the first ↩. That would explain why the Script Filter has an Inbound Configuration. So it is not autocompleting. Rather, it is reinvoking Alfred with different text, which it also understands. You can “trick it” (Unicode Workflow) by selecting the space and / and deleting both at once. Yes. See autocomplete and mods in the Script Filter JSON Format documentation. No. The user’s theme is independent from Workflows. There’s no official API. See alfred-cal for a Workflow which does something like that by checking the font’s width.

Even better! That was a later addition.

@gul-iMac Whatever happens in Safari is between it and the 1Password browser extension. The Workflow doesn’t affect that at all.

Add a Conditional Utility. Leave it with the default of if {query} is equal to which translates to “if input is equal to <empty>”. Then connect the top output to an Argument and Variables Utility with {clipboard} as the argument. Like so. Keep in mind that when nothing is selected, it’ll still work but you’ll hear a sound. That’s unavoidable, as it’s coming from macOS erroring when you can’t copy the selection.

Thank you as well for keeping at it and being so quick with debugging feedback.

As I said: In which that won’t happen. It’s described above: That’s just it. Delete two objects; put a new one in their place. The learning process involves reading instructions and trying to replicate them.

For image conversion and other manipulations, there are several ready-made Automation Tasks. They use sips under the hood.

I believe you! But because this would affect every Workflow and you’re the only reported case, there has to be something on your machine which is making the difference. Our goals is to figure out what. Just had a thought. Go into System Preferences → Security & Privacy → Privacy. Scroll down to Automation. Check if Terminal.app is ticked under Alfred.

They’re not—they are separate arguments in an array. But environment variables can only be strings, so to save the list of files in a way that is parseable by a Run Script down the line you need a join character to later split on. Check the second line of the top help text in an Arg and Vars object: It’s the Arg and Vars making it tab-separated, not the Universal Action.

Welcome @TekEgg, If the only thing you’re doing is connecting a Keyword Input to an Open URL Action, it will behave the same as a Custom Web Search. But say you add a Split Argument between them. Suddenly you can give your Keyword a bunch of words separated by commas and the open URL will open the site that many times, once for each word. One extra object, many more possibilities. And that’s a single example; Open URL also allows Using Variables in Workflows in addition to {query} and you can define what part of your input should be URL-escaped or not. Plus, you can tell the Workflow to automatically do stuff after the website has opened, like wait for the page to load then press a key combination. In sum, a Custom Web Search is like a fast way of making a really simple Workflow for opening a web page. When you need more control or to perform several actions, use the Workflow editor.

You’re not, that’ll work too. But @pankajsz already had partial code which looks like they wrote it themselves, so I opted to fix it in their chosen language instead of rewriting as a shell script. Python is far from being my language of choice, but when you’re learning it’s better to correct the course than veer wildly. With the former you can try to understand what changed and add it to your arsenal; with the latter you’re left with the proverbial fish but not the fishing skills. Not to say that I disagreed with sharing the Zsh code; I don’t in the slightest. Merely explaining my choice in this situation since you asked. In a case where the Python code had to be fifteen lines and the Zsh code three, I’d have eschewed the Python route. Technically you don’t even need the Run Script and Split Args, you can replace both with the Get Path Basename Automation Task that went live with yesterday’s 2022.8 release. That I did mean to mention but forgot.

Looks like the link got cut off. Try now.

You should hear “hello” and also see the command in the Terminal. The next thing to try is resetting your Terminal settings. I that doesn‘t work, there’s something about your macOS setup which isn’t working correctly, and the question is what.

You can build complex Workflows without knowing how to program. Plenty of people do. New features in Alfred 5, like Automation Tasks, take that goal even further. All you need is patience and logical thinking, both of which can be trained. The documentation is comprehensive, and you can learn about any object fast by pressing the (?) on their editing windows.

By running that in your Terminal, your setup should start and you’ll bypass the problem. For a more permanent fix, we need to narrow it down. Try this Workflow. With the Terminal closed, open Alfred and run testterminal. What happens?

Do it with the Workflow Debugger open and paste here the messages.

Right click → Show Package Contents.