Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by tbrown

  1. @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.
  2. 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.
  3. Still playing around. I can use the workflow to call another Keyboard Maestro macro by hotkey, just not the one I want!
  4. 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.
  5. 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 f
  6. 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.
  7. By the way, the scripts work and properly find my Keyboard Maestro macros.
  8. 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 "Alf
  9. Nice workflow, thanks. A couple of comments: Some functions, like factorial (5!) for example, don't work. Any way to change trig functions to use degrees, not radians? Any way to set variables for calculations? I realize the last two are probably not trivial, but hey, you have whetted my appetite.
  10. 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.
  11. 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--
  12. 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.
  13. 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.
  14. 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?
  15. 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.
  16. 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
  17. 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 fo
  18. 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
  19. 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?
  20. 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.
  21. Okay, you've got me dazzled. How in the world do I set the environment variable to avoid opening new tabs? I have set it in .profile and in my .bashrc so that it is correctly set in bash terminal windows, but this has no effect on the Alfred shortcut. It still opens new tabs. I have searched and found nothing clear about how to do this. Weird stuff like creating .plist files. What's the best way? BTW, I love this workflow. Thanks for posting it.
  • Create New...