virpio

So what I am seeing is, I set up a Script Filter that reacts to a keyword, say "foobar", and I give it a placeholder title of "Open current foobar", and then in the script filter just return a list with a single item that has a title of "Open foobar from <path>". Now when I type "foo", Alfred shows the list as the top and most likely target, but its title says "Open current foobar". I first have to hit return for it to start showing the result and with that "Open foobar from <path>". I then have to hit return again to actually trigger that action. What I'd want is the original entry just showing "Open foobar from <path>" right away and just having to hit return once to trigger that action. Am I setting the wrong options here for that script filter?

With a script filter this becomes a two step thing though I believe. If I add a script filter that always returns just a single entry, during autocomplete when I start typing the command (say I have foobar as the name and I type foo) it completes with the placeholder text and only if I hit return it then switches over to the list entry. I only have a single entry all the time so the initial step is one I don't really want / need.

Hi, I have a workflow where a script returns a path to open. This works just fine. But ideally instead of naming my workflow something like "Open current destination" I'd rather name it something like "Open <resolved filename>". So basically I want the script to execute _before_ I hit return and then put the result in the name of my input trigger. Is this possible somehow? —Michael

🤯 I had no idea! Thank you!

I'm more talking about the fact that you can actually put a script inside of the workflow folder without Alfred touching that + Alfred invoking the scripts so that they are running from inside that folder. Having even just a button that would open this folder would make it clearer that this is actually something you can do, although what I would love to see is to have these files actually be represented in the grid similar to a script phase.

omg god, thanks! This is SOOO helpful, that should be something you can do via the UI.

Hi, I have a workflow with plenty of different actions all evolving around a similar data set. E.g. a lot of workflows start by first having the user select from a list of available data to act up on. Right now I do this by having a Script Filter as a start which then has a bash script to generate this list, and this bash script I copy around over and over. After the user chooses an entry from the list, I then need to run another script to resolve that item to a path or URL to then do something with it. Since this is a lot of copy and paste and it makes it really annoying when you find a bug in the script and have to then fix that same issue in 10 places, I would love to have a bash script that is shared in the workflow that just exposes a couple of functions, so that in the Script Filter action, I could simply say something like getSourceList() and then in the next script phase resolveIdentifier(${1}). Is this possible somehow? I don't seem to find any way to add a shell script to a workflow that is imported at the beginning of every script in the workflow. Thanks for your help!

If there's any more debug info I can gather, let me know. Happy to help. In this case, I am almost certain I probably never granted Alfred full disk access in the first place as I am typically very restrictive with these kind of permissions unless I see a clear benefit and use case for me. I'm not super familiar with these APIs, but my understanding is that even without full disk access, Alfred should always be able to access a file I pointed it to previously via an open dialog. Also given that this happen immediately after I choose a config file location and given that Alfred shows the correct key command in its preferences it seems to be able to read the config file. So it sounds to me like there might be something else going on here that's a bit more subtle than Alfred being unable to read the config file.

Fair point. I just deleted the file at ~/Library/Application Support/Alfred/prefs.json and restarted Alfred. I verified that everything worked again (key command and workflows) and then told Alfred to sync to ~/Downloads, which is not on iCloud Drive. It immediately stopped working again after the restart of Alfred. The key command is back to option+space instead of cmd+space and no workflow can be found. So I started looking through the other aspects of the configuration on both systems and finally found the issue: On the Mac that wasn't working I haven't granted Alfred permission for Full Disk Access. I am not sure why this is showing in this way since it can clearly read the config file without issues (it shows the correct key command and all my workflows in the preferences inside Alfred, it just doesn't honor them). So this still sounds like a bug in Alfred to me, but at least I can now sync my config between different Macs.

I have to scenarios that both failed which makes me believe it is probably not an issue with the preference bundle itself: I first tried to initiate syncing from this machine by choosing a folder in iCloud Drive and let Alfred copy over the preference bundle to that location. It immediately stopped recognizing the key command or any of my workflows. I looked through the preference bundle and it looked like my workflows were in there. Console.app was not showing any error logs for Alfred. I then reverted back to using a local file simply by deleting that preference file and Alfred was immediately back to normal. I now initialized syncing on a different Mac in a different folder and that Mac was (and is) working like before. The hot key worked, all my workflows are there etc. I then pointed the original Mac back to that file and it again immediately stopped working, not recognizing the right key command and not being able to recognize any of my workflows. Looking at the access rights for that preference bundle on the machine that has the broken behavior I see this: drwxr-xr-x@ 5 <username> staff 160 Jul 22 11:45 Alfred.alfredpreferences This, I believe, is the way it should be? I can grab other debug logs if you need them, and send them to you via a support email if you tell me what to grab.

So basically Alfred preference sync is not working with iCloud Drive? That sounds problematic given that there is no cloud sync in Alfred and it even explicitly mentions DropBox as a way to sync config files. Also, given that this happens immediately after turning on syncing and choosing the file, after making sure everything in that folder is synced, I think there is most likely more to this issue than just that. It's not complaining that it can't read the config or anything (and as said, it is fully synced and local), it just seems to refuse to honor a lot of things in that config file. None of my workflows are executing and the hotkey I set up for Alfred doesn't work. Even if I configure it again in Alfred. For me it is always stuck to option+space, no matter what key combination I actually configure (and what is shown in Alfred).

I have the exact same issue on my machine, while it works without issues on another machine.