vitor

The only alternative at the moment is for Workflows to have their own update mechanisms (which several do).

I recently had an issue where Alfred was getting the result I didn’t want stuck at the top, and no amount of retraining was working. What fixed it for me was going into Alfred Preferences → Advanced and then unchecking and rechecking Top Result Keyword Latching (under Learning).

The issue is your script is missing the shebang line.

Setup an Argument and Variables Utility between them and make the argument empty.

Try Afloat or Fenêtre.

Welcome @mrtechnique, What you’re asking about is how to work with a specific Workflow. You’ll have to find its original thread/post/author and ask there.

List the contents of your ~/Downloads directory and act on them. Call the workflow with rdn to sort from the most recently modified, rdo for the reverse; rda to sort from the most recently added, rdz for the reverse. To act on the selections, use the standard Alfred shortcuts. You can activate file actions, dive into directories, preview files, add them to the file buffer — whatever you want to do that is supported by Alfred. Download | Source

Update. When showing directories, do not remove text after periods. To update, download the latest version (same URL) or wait a few days and it’ll prompt you to on next usage, since it uses OneUpdater.

Only on a case-by-case basis. You can, for example, add your PATH line to the top of the script. Think of it as a blank shell every time.

Open the debugger, set the log output to “All Information”, and run your Workflow. You’ll likely see line 3: python3: command not found. Alfred doesn’t know about your shell setup, just like your shell doesn’t, by default. You likely have some PATH line in your shell’s configuration files that tells it where to find python3. So Change that to /usr/local/bin/python3 or whatever its path is (check with which python3 in a Terminal) and it should work.

Welcome, @Ninzero, We can’t properly help you without access to your Workflow. Debugging can already be hard with access to the code, and you’re asking us to guess yours from a description. There are multiple places where your code or Workflow setup may be going wrong. Without looking at it we’re shooting in the dark, which is a waste of time for everyone involved (including you). Read the Reporting Problems with Workflows topic, as it gives a nice overview on how to build an effective report.

Can’t reproduce your issue. It works fine with me. You should check if other app (like another clipboard manager) isn’t causing the duplication problem.

"valid": false → "valid": true.

For the forum, here are some screenshots of the app working:

Control SandwichTimer from Alfred, to run pomodoros and timers. If you don’t have the app installed, invoke :sandwichtimerupdateapp to get the latest version. See the linked page for screenshots of the app in action. Call pomo or set a keyboard shortcut to start a pomodoro timer. If another is already running, it’ll be aborted. timer will let you set as many timers as you want, for the specified amount of time. With both options, actioning with ⌥ will quit all instances of the SandwichTimer app. Download | Source

What’s the problem with the Workflow? The top part works fine.

The problem is the var_. Remove those and it’ll work.

I don’t understand your question.

This is how it should look:

Great! Not sure why having them together is not working on 10.13, but what matters is that it’s now working for you. Marking as solved. Enjoy! And welcome to the forums.

@MarcG Seems like the utility is still the same. Since your error is somewhat bizarre, this looks like an oddity in your personal setup. Just to get more data, what’s the result of: /usr/sbin/screencapture -i -P '/tmp/test.png'?

Tip when debugging: never say “latest” but always the exact version. When you say “latest” we don’t know if you mean the latest beta or stable version, nor do we know if you’re actually on the latest version. You may think you’re on the latest version but me mistaken, or might be a version behind because the auto-update hasn’t kicked yet, or I may not be on what I think is the latest version but isn’t, or a multitude of other reasons. It also does not help someone who comes later with the same issue, as they’ll have no idea if their version matches yours. That said, no need to fix it this time, as the issue is not with Alfred. I’m on 10.12, so it’s possible screencapture changed some option between versions. In a Terminal, do pbcopy < <(man screencapture | col -b). Then paste the result somewhere like pastebin, so we can see the manual for your version. @juliosecco Are you also on macOS 10.13.4?

We can’t properly help you without access to your code. It isn’t even clear from your description what you want to do. Ideally, you should try to build a Workflow and then ask us about where you’re stuck. Read the Reporting Problems with Workflows topic, as it gives a nice overview on how to build an effective report.

You’re making it more complicated than it needs to be. The python Run Script is unnecessary, as is the duck Keyword. Just have the List Filter with the options spelled out and the bash Run Script.

Open the debugger, set the log output to “All Information”, and post the output. Run the command in a Terminal. What happens? What is your versions of Alfred? What is your versions of macOS?