vitor

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?

If you want tab to move through controls (and not just text fields), you have to tell macOS itself to do it: System Preferences → Keyboard → Shortcuts → Use keyboard navigation to move focus between controls (at the bottom of the window).

I haven’t messed with Photoshop Droplets in over a decade, but unless they’ve changed they’re just apps to which you can pass arguments. What you want should work by adding a Hotkey Trigger (with Argument: Selection in macOS) to an Open File Action (leave the left side empty, and on the right side drop the droplet). Bonus: add a File Action Trigger and you can also get to it from Alfred’s file navigation and the Universal Actions shortcut. Alternatively, just use the Convert Image Format Automation Task, no Photoshop or droplet needed.

Welcome @Monte Lin, The Workflow has existed since 2013, so “finally” doesn’t really apply! It’s also not a very popular Workflow (probably, I don’t have real numbers) because it’s not something people need that often. Plus, it requires weird solutions to get right in that many shells. All that makes it so it’s the right decision for Alfred not to have this natively. Alfred doesn’t load the user’s environment by design, it’s a feature. This is exactly what Workflows are for. Works for me. Open the debugger, set the log output to “All Information”, perform the failing action, and post the output.

Alfred doesn’t load your shell’s startup files. See Understanding the scripting environment.

Tell the Conditional to matches regex and use ^!b as the match (i.e. text starting with !b). Then use a Replace Utility (again matching regex) to replace ^.*? (there’s a space at the end) with nothing. I.e. it deletes everything from the start of the text until—and including—the first space). This is sounding a lot like an XY problem, though. To get proper help describe what the final result is supposed to be instead of the steps you’re envisioning to get there. It’s likely there are better approaches for what you want.

Shouldn’t be. I just tried it and it works in any order. Contacts results, or results in general? You have to use the Keyword defined in the Workflow’s File Filter to call it, it doesn’t take over your default results.

@YuTang It seems installed correctly. It’s not supposed to be in /usr/bin/python. It isn’t clear why you have it in both /opt/homebrew/bin and /usr/loval/bin, though. Did you install Homebrew with Rosetta in the past? To confirm, are you on Apple Silicon? What’s the output of ln -s /opt/homebrew/bin/python? In addition to reinstalling Python 2, you also need the updated versions of those Workflows (but always check the alternatives first). In the case of the Omnifocus Workflow, you’re on an old version anyway. The developer has converted that from Python 2 to Node.js. That won’t work because of SIP. And that’s a good thing, because you shouldn’t be putting stuff the system doesn’t expect in /usr/bin.

Make sure you download from the correct releases page. @giovanni The Downloading section in the README is pointing at Dean’s releases.

It does. On the Basic Setup tab of the File Filter, drop a markdown file on the File Types area. Then go to fields and [+] → kMDItemTextContent, which search inside files.

Alfred Preferences → Advanced. Look on the right side (third, fourth, and fifth popover buttons).

You’d have to use a Script Filter and parse them yourself. The task sends the paths along to the next object (e.g. connect them to a Send to Trash and do it to all). Listing them is a different thing. What you’re asking is equivalent to a File Filter with the scope set to a specific directory. You can’t have ⌘C, but you can have ⌘↩, or ⌥↩, or any combination of fn⇧⌃⌘⌥ with ↩. Connect a Copy to Clipboard Output and double-click the circle on the connection. In the palette to the right, tutorial 4 on Getting Started explains it.

It does not. Your connections, Keywords, Terminal Command, Open URLs and even the organisation of your Hotkeys will all remain in place. Plus, presumably you’ve added those shortcuts for your use as well. Alfred as always worked this way. Before importing a user can’t know if the Hotkeys the Workflow has will conflict with their own. Accepting random Hotkeys would likely lead to undesirable results.

By design, Alfred strips Hotkey values when the Workflow is imported. This is precisely so when adding a third-party Workflow, you won’t have your shortcuts overridden without a say. In other words, your keyboard shortcuts are unique to you, anyone importing the Workflow will add their own.

Connect a Keyword Input to a Launch Apps and Files Action. Alternatively, type p and scroll down until you see Apple Photos. Act on it (↩). Do that 2 or three times in a row, and it’ll become the top result. Then do the same for ph and Photoshop. Alfred naturally learns from these choices.

It doesn’t do it by design. Showing every file from the start has performance implications. That’s how the File Filter works. * will show everything, and *ext allows you to search for files with a specific extension. You can also use the File Types area in the File Filter to restrict the search to specific file types.

That’s the perfect use case for a File Picker User Configuration. Without changing anything in the Workflow itself, you can delete the Workflow Environment Variable and make this config: Which yields: Allowing to pick the coupon file though a macOS file dialog.

Great! Shouldn’t need the first one, though, as the second one already returns the URL upon closing the tab.

Thank you. A nice weekend to you as well.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Make sure Alfred is present and with a ticked checkbox under System Preferences → Security & Privacy → Privacy → Accessibility. If it is already there and checked, remove it an add it again (macOS occasionally screws that up), then restart Alfred.

Have you seen the annotated screenshot?

Temporarily create a new user account on your Mac, set up Alfred on it, and try again. Can you still reproduce the behaviour?