Jump to content

manusz

Member
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

manusz's Achievements

Helping Hand

Helping Hand (3/5)

1

Reputation

  1. That is not what I am seeing here, so definitely a different bug. All I can suggest is to rebuild the Spotlight index. If you have not do so already, Alfred offers the tools to do that under the Preferences - Advanced.
  2. Are you saying that, when Spotlight looses track, Alfred can not find what you are searching for?
  3. That is too bad..... It seems that you have been bitten by different bug than the one that got me. if I find a solution I will let you know.
  4. Good luck and keep us posted please. I am highly interested in a real solution for this issue.
  5. I had a similar issue with Spotlight. After a week of trial and error troubleshooting it turned out that the issue did not occur when I logged in on my Mac account with the password. It seems that the fingerprint log-in causes some hiccup. I still don't know the root cause of this, but not using the fingerprint sensor (nor Apple Watch if you have one) may be a workaround in your case too. Mind you, Alfred uses the Spotlight index, so if Alfred produces correct results the Spotlight index is OK. What remains is that the Spotlight search engine starts producing incomplete results.
  6. I did not expect to see the Lock Screen when I woke up the screen. That may be caused by the System Setting Require password after screen saver begins or display is turned off which I have set to Immediately. From now on I will use the ⌘↩ key combo as that triggers the action I expected. Thank you for your help!
  7. When I issue Coffee (without parameters) in Alfred, walk away and return after 20 minutes, the screen is dark. Now, when I touch the mouse, I am greeted by the Lock Screen and I have to provide my password or fingerprint to log in. I see this on 2 M1 Machines.
  8. It seems that the Coffee workflow does not have any effect on Sonoma 14.1.1. This Mac upgraded from Sonoma 14.1 last week, I am pretty sure Coffee kept the machine awake then. For what it is worth I copy the debug data below. As far as I can tell the workflow runs just fine, so perhaps Apple changed something in the last Sonoma release? [22:11:24.636] Coffee Coffee[Script Filter] Queuing argument '' [22:11:24.713] Coffee Coffee[Script Filter] Script with argv '' finished [22:11:24.719] Coffee Coffee[Script Filter] {"rerun":0.5,"items":[{"title":"Turn On","subtitle":"Keep awake indefinitely","arg":"coffeecoffee_process_anchor on","icon":{"path":"icon_alt.png"}}]} [22:11:24.855] Coffee Coffee[Script Filter] Processing complete [22:11:24.861] Coffee Coffee[Script Filter] Passing output 'coffeecoffee_process_anchor on' to Arg and Vars [22:11:24.863] Coffee Coffee[Arg and Vars] Processing complete [22:11:24.864] Coffee Coffee[Arg and Vars] Passing output 'coffeecoffee_process_anchor on' to Junction [22:11:24.865] Coffee Coffee[Junction] Processing complete [22:11:24.866] Coffee Coffee[Junction] Passing output 'coffeecoffee_process_anchor on' to Run Script
  9. Thank you for enlightening me! I have read the links you provided, I do understand now what is going on under the bonnet and why I see what I see.
  10. A n00b question from a new Alfred user..... I see an unexpected result when I run this workflow. When I compare the output from the workflow to what is reported when I use System Settings - General - Storage the results differ by approximately 35 GB, see attached screenshots. This is on a M1 MacBook Air running Sonoma 14.1.1 Is there anything I can do to get the results more in line or is it just misinterpretation from my side?
×
×
  • Create New...