vitor

When asking for help with a Workflow, please upload it somewhere as we can’t properly help you without access to it. Debugging can already be hard with access to the code, even more so when all we have is a description.

Missed that one. Now fixed the repo in the Workflow. Just python works and will avoid the same issue in the future (or if you install the Workflow on an Intel machine).

Adding that to the regular search would probably make it slower. It’s the kind of thing which should be a Workflow instead, even if that means requiring a keyword. Here’s a Workflow which lists all running applications. Pressing ↵ on any will switch to it.

Welcome @Blacksmith, Probably yes, but it may depend on how the data is embedded. Here’s something you can try: run the troubleshooting to view file metadata and see if the information you want to search for is there. If it is, great! It means Spotlight indexes the data and Alfred can see it too. If you don’t see what you’re looking for, it will probably still be doable (can only say for sure after examining a couple). It means understanding how the data is embedded and how it can be read, then making a Workflow for it. We can help with that too.

Update. It will specifically not close the window on special actions. 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.

Update. Made some changes and fixes for it to run smoother. But in particular, what you might notice: Turning off will now only terminate itself. This means that if you have other caffeinate processes running from other entities, those will be left alone. When running again to turn it off, if you previously picked a time frame it will tell you when it’s predicted to auto-turn off. Keep in mind that due to the nature of how Apple’s own caffeinate measures its timeout, the time might be somewhat off. The shortcut for preventing the display from going to sleep changed from ⌥ to ⌘. 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.

Welcome @CatsAndCoffee Can’t reproduce at all. Try downloading it again, it was updated recently. It’s useful that you give the machine details, but the Python 3 part is irrelevant. For one, the point of these Workflows is that they have to use Python 2. If you haven’t followed the knowledge base article to install it, these won’t work. But no macOS machine comes with Python 3, so saying it’s running but not how it’s installed is insufficient information. Again, it doesn’t matter in this case, only pointing it out for future debugging.

I cannot force notifications on users, nor would I want to. Permissions for notifications is something you have to control yourself, and that is a good thing.

This makes the code more complex, because in addition to asking the browser to open the window now it also needs to know which browser to do it for. Make a Run Script Action with Language /usr/bin/osascript (JavaScript), and in Script, paste: const frontmost_app_name = Application('System Events').applicationProcesses.where({ frontmost: true }).name()[0] const frontmost_app = Application(frontmost_app_name) frontmost_app.includeStandardAdditions = true const chromium_variants = ['Google Chrome', 'Chromium', 'Opera', 'Vivaldi', 'Brave Browser', 'Microsoft Edge'] const webkit_variants = ['Safari', 'Webkit'] if (chromium_variants.some(app_name => frontmost_app_name.startsWith(app_name))) { frontmost_app.Window().make() } else if (webkit_variants.some(app_name => frontmost_app_name.startsWith(app_name))) { frontmost_app.Document().make() } else { throw new Error('You need a supported browser as your frontmost app') } function run(argv) { frontmost_app.openLocation(argv[0]) } That takes in whatever URL you send from the previous object and opens it in a new tab in the frontmost browser app, whatever that is (again, not Firefox). If you want it to open in a new tab and in a new window, use this instead: function run(argv) { const frontmost_app_name = Application('System Events').applicationProcesses.where({ frontmost: true }).name()[0] const frontmost_app = Application(frontmost_app_name) frontmost_app.includeStandardAdditions = true const chromium_variants = ['Google Chrome', 'Chromium', 'Opera', 'Vivaldi', 'Brave Browser', 'Microsoft Edge'] const webkit_variants = ['Safari', 'Webkit'] if (chromium_variants.some(app_name => frontmost_app_name.startsWith(app_name))) { frontmost_app.openLocation(argv[0]) frontmost_app.Window().make() } else if (webkit_variants.some(app_name => frontmost_app_name.startsWith(app_name))) { frontmost_app.openLocation(argv[0]) frontmost_app.Document().make() } else { throw new Error('You need a supported browser as your frontmost app') } frontmost_app.openLocation(argv[0]) }

Here’s a Workflow for it.

The first thing to understand is that you can’t do this with the default custom searches, you must recreate the ones you want in a Workflow because you’ll need to run code to open the new browser window. So you want it twice with one run?

It’s neither; it’s a directory you can freely inspect by right clicking then “Show Package Contents”. You can just backup the workflows directory from there, but it’s bound to be the biggest one anyway; it makes sense to back up it all.

In theory yes, but in practice a blanket search like that delivers a lot of undesirable results, such as things in ~/Library generated by apps. Those searches work better when focused to specific directories, which is why it’s the solution I ended up with for RecentlyAdded.

Welcome @bo9, It depends entirely on your browser. You need to ask it specifically to open a new window with the search. Here’s an example which searches Google with Safari. If you need something different, please specify throughly what you want to accomplish and which browser you’re using. Quick note: if it’s Firefox, no luck.

@Mr Pennyworth’s Fuzzy File Search might just be what you’re looking for.

But you’re still posting in this thread. You should be posting on the thread of the Workflow or its GitHub page, or wherever you downloaded it. Again, screenshots don’t help, they don’t bring us closer to knowing what that is and we can’t see the Workflow. Without a link, there is nothing to be done. I asked specifically if you had tried another Workflow:

See Syncing Your Alfred Settings Between Macs.

Try this one. It’s untested.

Not that part. The second paragraph.

When making a request or a bug report pertaining to a specific workflow, please do not open a new thread to discuss your issue. Making a new thread, while it seems like it’ll give your problem visibility, fragments the discussion and makes it less likely the author and users of the workflow (the people who can help) will see it. Please read the Reporting Problems with Workflows topic, as it gives a nice overview on how to make a report with a better chance of being addressed. I don’t know what that Workflow is. If you don’t at least provide a link, we’re limited in how we can help. Have you tried an alternative?

A Copy to Clipboard Output can paste text directly, which is faster and less error-prone. Unfortunately, using AppleScript to keystroke text doesn’t work too well in languages with diacritics.

If what you want is to send the commands for them to be executed on the target machine, you give them as another argument to the SSH command. As in: ssh 'xxx@yyy' 'osascript -e "tell app \"System Events\" to restart"'

It isn’t working because you’re entering an interactive SSH session and presumably not exiting, so the other commands never have a chance to run. What exactly are you trying to do?

Please avoid bumping without new information, especially so soon. What is required is a command-line way to do that. Once you find it, we can help you integrate it into Alfred. I looked into it briefly on the weekend and didn’t find anything. I doubt it exists and it may not even be doable with the APIs Apple provides, but it might.

Welcome @DomS, Never say “latest” but always the exact version. With “latest” we don’t know if you mean the latest beta or stable version, nor do we know if you’re really on the newest version. You may think you’re up to date but be mistaken, or might be a version behind because the auto-update hasn’t kicked yet, or we may be on what we think is the latest version but isn’t, or a multitude of other reasons. “Latest” also makes it difficult for people who face the same issue later on and find the conversation, as they’ll have no idea if their version matches the one in the report. That is covered in the second post, with links.