tbrown

I'm pretty sure that this workflow just doesn't work on Alfred 5. the python code associated with workflow is actually running workflow.py for Alfred 2, but has code (not referenced) for Alfred 3. These python files seem to have lots of problems in my environment.

I know this is pretty old, but I am trying to use Alfred-Cheat (or Alfred-Cheat2 with Alfred 5. The 'cf' command works--it activates the "configure your cheat directory' command in Alfred. However, the 'cheat' or 'cht' keyword is not recognized by Alfred. Why?

thanks for the tip. I fixed the problem by changing the scope of Alfred's search by dragging Macintosh HD into the scope field. Now the workflow finds the directory. Migration Assistant did not do me a lot of favors in this case.

I just upgraded to a Mac Studio and am running macOS 12.3. although the workflow sort of works, it now will not find directories not at the top level of my user directory. For example, it will find /Users/tbrown/Downloads when I type "fo do", but it will not find /Users/tbrown/Downloads/irc' when I type "irc". It used to and I'm not sure when it quit. Remotely possible it is the change to Mac Studio (I had lots of problems with Migration Assistant not transferring various permissions). It could also be the upgrade to 12.3. Any suggestions? My version of the workflow is .5.

Well, not noted here yet, so let me be the first. Agenda was updated and it fixes the calendar permissions problem. I downloaded it from the Agenda GitHub page and it now works! Thanks!

Agenda works well for me with respect to reminders. However, I am unable to access my calendar using it. Alfred4 does not appear under Calendars in Privacy and I don't know how to add it. It looks like Agenda should have prompted for that when I first ran it. I did get the standard failure when I first ran Agenda, and I authorized it and now I can access Agenda with the Alfred keyword 'ag'. However, agenda only works for Reminders (and works very well!). If I try to create new event, it tries to create a reminder in the list "Home" which is the name of my default calendar (which I set in the setup of Agenda). If I run agenda and select "Calendars", the Alfred command line clears, and "Show Calendars" briefly appears as a choice, then disappears and nothing happens. I can type stuff in the Alfred prompt, but return does nothing and I must use ESC to exit Alfred. I suspect the workflow doesn't have access to Calendars (Alfred doesn't). How do I fix this? I did try deleting and reinstalling, but no change.

@Andrew Yes, the lock command works when invoked from Alfred. I don't think this is an Accessibility issue. @deanishe I'm not sure how you define "(non-system) global assignment". I played around a bit and found, for example, that on my system, I can invoke the screenshot function by dispatching Shift-CMD-5 with the Alfred workflow, but I cannot invoke Mission Control by dispatching the Ctrl-UpArrow key sequence. So, it's all a bit odd to me.

Okay, I have solved the immediate problem of running the Keyboard Maestro macro "Trigger Macro by Name". Instead of trying to run the macro by sending the hotkey, I found that Keyboard Maestro will create an apple script that will run the macro. So I changed my workflow to run the script and it works properly. I still would like to understand why using the hotkey method doesn't work.

Still playing around. I can use the workflow to call another Keyboard Maestro macro by hotkey, just not the one I want!

I read another post that suggested I remove Alfred from privacy settings and then put it there again. No joy. It is also true that this is not a general failure. If I used the same workflow, but change the hotkey to be one that is used in Scrivener, for example, Alfred properly issues the hotkey and the key is accepted by Scrivener. But I can't get anything to happen (other than a faint sort of beep) when I try the hotkey for Keyboard Macro to run a macro. And, to reiterate, I am running this on an M1 Mac mini, with Big Sur 11.1.

Since the Alfred-Maestro workflow doesn't work on my M1 Mac mini, I began using Keyboard Maestro's "Trigger Macro by Name" macro to find and execute Keyboard Maestro macros. However, I can't remember the hotkey for this, and would rather just execute this function from Alfred. So I made a workflow, triggered by keyword 'km' which then feeds into a Dispatch Key Combo instance which issues the hotkey to trigger the Keyboard Maestro "Trigger Macro by Name" macro. Simple! I have attached a screenshot of the workflow definition in Alfred. But it doesn't work. I figured out that I had to disable the hotkey for the macro, then set up the hotkey to dispatch, but the dispatch hotkey output function doesn't do anything. And yes, I did re-enable the Keyboard Maestro hotkey. I even changed the hotkey a couple of times. Currently the hotkey is set to F11 and it brings up the Keyboard Maestro macro properly when used. However, when I try to invoke this from my workflow, it just does nothing. What am I doing wrong?

thank you! I should have found the debugger on my own, but oh well. It does show what I expected, which is that Alfred does call the workflow, but the executable causes a segmentation fault. I will create a new issue in the GitHub repository.

By the way, the scripts work and properly find my Keyboard Maestro macros.

I have looked at Github issue here https://github.com/iansinnott/alfred-maestro/issues/26 regarding Big Sur. My issue is a bit different and involves compatibility with M1 Macs. The Alfred-Maestro workflow doesn't even trigger on my Apple Silicon M1 Mac mini. It is enabled, and the trigger is typing "km" in Alfred. But when I do that, it appears not to trigger the workflow, and all Alfred finds is other things, like Keyboard Maestro itself. It is possible that the workflow is being triggered, but fails--I don't know how to tell. The workflow uses a compiled binary "Alfred-Maestro" in the workflow directory. This is x86 compatible, not a universal binary. It is compiled by Go. This executable, when run from terminal on Big Sur 11.01 on my Apple Silicon based M1 Mac mini using Rosetta (arch -x86_64 ./alfred-maestro), gives a segmentation fault. I assume, since Alfred version 4.21 is not universal, and therefore runs under Rosetta, that everything it spawns will be run under Rosetta, including workflow stuff. I have compiled a number of programs I use frequently as ARM native. However, in this case, I have read of a lot of complexity in using Go on Apple Silicon and am a bit reluctant to dive into the weeds on this one. Also, since Alfred is not yet ARM native, I'm not sure building Alfred-maestro as a universal app would fix this. But I do miss this workflow and it is the only thing I use daily that I haven't been able to get to run on the M1 Mac mini. Do you have plans to look into this, or can you make suggestions as to what I could do?

I do this, but use sshpass like this: sshpass -p yourpasswordhere ssh pi@pihole 'pihole disable' sshpass is not installed on Macs by default. I installed using home-brew. Be sure you understand any security issues this may cause on your Mac.

I don't think this has anything to do with whether the apps in question are part of the OS installation. Also, at this point, although I have no idea why, I currently do not have the problem. I can now quit Preview, for example. For the last day or so, I have been able to quit any app I tried to quit. I have had other fascinating Catalina problems I have been trying to understand. One is that Better Touch Tool takes a lot of CPU time, and particularly, is directly related to causing the Dock.app process to periodically take a lot of CPU time. This results in stuttering in the UI--typing, scrolling, etc. Not running Better Touch Tool fixes this. Similarly, I have stopped using a number of other background utilities to see if they affected the CPU time issue. My system now runs quite smoothly again. It is quite possible that some strange interaction between Catalina and these utilities was causing the problem with Alfred and that is why it now works. These problems are very complex and have many interactions. I don't pretend to understand yet.

Turns out this is not quite as simple as I first thought. On my account, for example, Preview.app is in the Automation Preferences list under Alfred 4, but I cannot quit it. Pages is not, but I can quit it. Confusing, and I have no idea what the difference might be.

I tried with with another user, and you are correct. There are not entries in Accessibility or Automation Preferences, but Alfred can quit applications without issue. Also, having forgotten about 'forcequit' in Alfred, I tried that from my user account. While I cannot 'quit' apps not list in automations preferences under my account, I can 'forcequit' them without issue. Not something I want to do routinely, I expect, but interesting.

Since updating to Catalina, the 'quit' command in Alfred can't quit apps that are not listed as those that Alfred can control under System Preferences/Privacy/Automation. For example, on my system, I allow Alfred 4 to control Scrivener and I can quit Scrivener from Alfred. However, Kitematic is not listed and an Alfred command to 'quit Kitematic' does nothing. I can't figure out how to get other apps on this list do Alfred can control them. Dragging and dropping doesn't work to this panel. How do I fix this?

My suspicion is that the workflow I created and use will still fail on your machine, since it is still not signed by an Apple developer. I think it only works for me because I created it locally and I can write and manage and execute scripts on my own machine without Apple caring--hence the instructions for building on your local machine. I also am uncertain as to whether it is proper for me to share the modified workflow here.

There are many Alfred workflow that I use regularly that are failing for me after upgrading to Catalina. They fail with the message "developer cannot be verified . . .". See this thread, for example: I fixed that one by recompiling myself, on my machine from the GitHub source. For me, this verifies that this is a Catalina permissions issue of some type. Is there any way of fixing these errors without manually rebuilding these workflows on my own machine? I have verified that Alfred 4 is enabled for Automation (lots of apps, including terminal), accessibility and full disk access.

This one was really important to me. When I upgraded to Catalina, it broke for me with a warning about malicious code or something. I figured it was a Catalina permissions problem of some kind. Here's what I did to fix it: 1. Cloned the git repository at https://github.com/iansinnott/alfred-maestro 2. I had to install go, which I did based on these instructions: https://golang.org/doc/install?download=go1.13.1.darwin-amd64.pkg 3. Following the instructions to build Alfred-maestro, I ran "make pack" in the Alfred-maestro directory. 4. Didn't work. Futzing around, I found that, in the Makefile, Alfred-maestro was to be copied into the workflow directory, but the build created alfred-maestro-master. So I changed line 8 of the Makefile to read: @mv alfred-maestro-master workflow/alfred-maestro 5. Ran "make pack" again and it completed successfully. 6. Installed my new Alfred-Maestro.alfredworkflow. 7. It worked! I did all this in terminal. Took me just a few minutes and now I am a happy user of Alfred-Maestro again. I have not seen this issue with other Alfred workflows I use regularly.

I got this to work the way I wanted. This workflow uses bash scripts. However, one of the bash scripts adds osascript -e 'tell application "Finder" to activate' at the end to bring Finder to the front. I added this to others, like "fo" and "rf" and it works perfectly! thanks

My use case for this workflow is usually this: I am doing something incredibly creative (!) and I need to reference a document from somewhere. I do fo (folder name) or maybe rf (select recently opened folder). The folder opens in Finder--cool! However, Finder is in the background. If I run this workflow with Finder in the background seems reasonable that I want Finder brought to the front so I can look at what I asked for. Any ideas about how to fix this in the workflow?

Ha! Thanks. I didn't realize the environment variable was with Alfred. I was looking for a way to set it system wide on MacOS. No wonder I didn't find this. Works perfectly the way I want now.