Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Andrew

  1. @johnhamill I've actually made some changes today which will make it in to the next build which will prevent Alfred from clearing the buffer if the workflow makes any changes to the buffer contents during the action. This should allow you to keep the auto-clearing option enabled for general use, while still working for your workflow too. I can't give you timescales on when the next build will happen, but if you could keep an eye out for it and re-test when it happens, I'd appreciate feedback Cheers, Andrew
  2. @Chris Messina This is in the macOS System font with no option to theme. There are a few reasons I made this fixed, but it boils down to if there were some issue where a custom font in a theme somehow "broke" Alfred, then at least the update text would still be visible so the user could update.
  3. So this is actually a more complex issue that I had originally anticipated. Alfred is actually working as intended, but the behaviour doesn't match this specific case and I'm going to make a logic change to work better. It's essentially a conflict between Alfred clearing the buffer after actioning (option in Features > File Search > Buffer > Clear After Actioning), and the workflow changing the buffer contents during the action to the items you're actioning. I will be adding additional checks pre and post actioning to check if the workflow has changed the contents of the buffer, and not clear the buffer if the workflow has made any changes to the buffer.
  4. I'll look into this today, but please bear with me as I'm juggling quite a few technical things at the mo. This file buffer workflow object is more intended to interact with the buffer of files you see above Alfred's default results, but this is an interesting use for it. Off the top of my head, it could be that they are added to this, but the items output from the workflow object aren't correct for the config selection. I may end up rewriting the logic within the object during testing if there is a bug just to simplify things.
  5. @twhb As this is a somewhat complex corner case (Alfred can't know if the intended mount of a volume will ever exist, or indeed how long it may take for the volume to mount), it would be better to not have Alfred automatically launch at login and create your own script to delay the launch of Alfred.
  6. "File buffer contents" represents the current files in the file buffer. "Successfully added files" represents the files you're trying to add for the specific File Buffer objects (some files may not be added if they don't exist). If you're only getting files out of the buffer and not adding any for a specific buffer object, "Successfully added files" will be empty.
  7. @sudopeople your very first screenshot is a good example of why you can't just remove the .prefPane extension. The actual name of the item is provided by macOS to Alfred via the metadata index, and is localised to whichever language your Mac is set to. In your case, macOS should return "Printers & Scanners" for PrintAndScan.prefpane. When I recommend to clear Alfred's cache, this simply flushes Alfred's local temporary performance cache. When the underlying metadata index is malfunctioning, Alfred may be holding on to a cache of when the name was being passed back incorrectly, and this is a very fast first check which resolves the issue in almost all cases. Alfred doesn't index himself, he relies on the underlying macOS Index for file search data, and these localised names of folders, files, prefs and apps. Alfred's mechanism for rebuilding the macOS metadata index is via one of the only scriptable methods Apple supply, and I leave the technical aspect of this visible, as it's outside of Alfred's control and I want people to understand that they are performing a lower level macOS command. When using the shortcut in Alfred's preferences, Terminal opens and the following well documented macOS command is run: sudo mdutil -E -i on / The -E requests to erase the current store, -i on / ensures that the index is enabled on the main drive. In combination, these cause macOS to rebuild the metadata. This is in fact the first time I've heard of the Spotlight Privacy preferences being broken as per your last screenshot, so I believe your issues in macOS will be deeper rooted than the metadata index, and more towards permissions issues, or corruption in your install of macOS itself. I also think that the issues you're seeing now would have manifested themselves sooner or later regardless of using the rebuild (i.e. Alfred doesn't interact with the Spotlight Privacy prefs in any way). I hope this help you and others reading this understand that rebuilding the metadata should be a safe exercise if you're experiencing file search or naming issues. Please let us know how you get on, or if you find a solution. While the issue you're experiencing is rare, it's good to build a wealth of information on this forum which can potentially help future users. Many thanks, Andrew
  8. @sudopeople try typing reload into Alfred to clear his caches. If this doesn't work, you may need to rebuild your macOS metadata (shortcut in Alfred's Advanced prefs) as Alfred gets the names for these from macOS itself. Cheers, Andrew
  9. Alfred doesn't do anything which would prevent your Mac from sleeping, and interestingly, when using the sleep command, Alfred simply simulates the shortcut for the menu option you're seeing the issue with. I don't believe Alfred is the issue in this case. Are you still experiencing the issue?
  10. @aaron_h I'm constantly making accessibility improvements to the workflow editor, and in the current it should read the contents and selections of the editor. When initially creating the workflow editor a number of years back, I created it as a fully bespoke component. It turns out that this doesn't intrinsically work with the macOS Accessibility APIs, and any accessibility I've added has also had to be fully bespoke. A current limitation is that it is still mouse driven for editing, which I fully appreciate isn't aligned with the needs of VoiceOver users. One big plan I have is to overhaul the editor to contain subview items (instead of simply drawn and rendered items), which will allow for each item to have accessibility context within the macOS Accessibility framework. This overhaul would also include full keyboard navigation for the objects. For now, to get to any hotkey field in Alfred, use the ? command in Alfred's search. For example, open Alfred and type "?workflowname hotkey", if the top item returned isn't the one you want, press the down arrow until it is, then when you action this result, it will open the workflow editor to the specified workflow and pre-select the hotkey object. You can then press return to open the configuration for that object. Note that while testing this, I realise that the VoiceOver for reading the selected hotkey in Alfred's results doesn't also read the workflow name. I'll fix that in the next build. If this doesn't satisfy your needs for now, get in touch on our info@ address and we’ll help you out further. Cheers, Andrew
  11. @Radek Salomon This is a limitation of the macOS Address Book API Alfred uses. In the future, he'll be updated to use the Contacts API which will allow for diacritics. Alfred has an option (visible to Powerpack users) but off the top of my head, it is also available to non-Powerpack users if you edit the plist file in the following location: /Library/Application Support/Alfred/Alfred.alfredpreferences/preferences/features/defaultresults/prefs.plist The plist needs to include the showContactsUsingMetadata key set to true, as per below: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>showContactsUsingMetadata</key> <true/> </dict> </plist> If you have a Powerpack, this option is in Alfred's Preferences: Prefs > Features > Contacts > Advanced > Use Spotlight metadata for searching contacts Cheers, Andrew
  12. @dfay for now, the logic is quite simple in that if the bin is missing from the original location (i.e. php is no longer installed by macOS in /usr/bin/php), it will look in those 2 alternative locations. It does this for all the selectable languages in Alfred's Run Script for future proofing. If you want to use an arbitrary language, I recommend using the "External Script" option.
  13. Just as a quick update on this... if users on Monterey could update to the 4.6 b1263 pre-release, this should now have what I discussed in my previous post. Let me know how you get on
  14. @craw The screenshot you posted only refers to the top level Alfred Preferences folder, not the contents. There may be some readonly contents within this folder causing the issue, and as @deanishe mentioned, it could be your sync software causing the issue (I see the folder is Qsync). Take a look at this guide for repairing permissions: https://www.alfredapp.com/help/troubleshooting/preferences/ Note that you'll need to update the paths to be relevant for your preferences.
  15. If you mean you don't want it going in Alfred's clipboard history, use this option in the Copy to Clipboard object:
  16. @Ben C We have an internal tool for migrating Alfred 2 snippets to Alfred 4. Pop an email to our info@ address and I'll share it with you Cheers, Andrew
  17. Just as a quick update on this, when I release the next version, the bin error dialog now gives a few more useful options allowing for workflow to be opened or disabled so you don't see the issue again: Alfred will also search for alternative paths when the macOS standard bin path is missing, e.g. for php Alfred will also look in: /opt/homebrew/bin/php /usr/local/bin/php I have some more changes I want to implement for the next release, however, there is a good chance I'll do an interim build in the next few days which will contain this change, allowing for macOS 12 users to use php workflows if they have an alternative php installed (e.g. via homebrew). Cheers, Andrew
  18. @andy4222 Sorting in universal actions is disabled by default, ensure to enable this here: My intention is to improve the sorting of universal actions to operate more like Alfred's default results, at which time, it will likely become enabled by default. Cheers, Andrew
  19. @Chris Messina it looks like this is still in the 1Password 8 plan: https://1password.community/discussion/122536/early-access-and-alfred
  20. @Mschuiling Just in case you were trying to reply to the Evernote topic @deanishe provided and accidentally created another topic, use the "Reply to this topic" button in the Evernote topic instead of Create Topic.
  21. @xattr You will be able to get most of the way there with a simple workflow in Alfred. Add a Hotkey or Keyword object to a workflow, then connect this to a Run Script object set to osascript (AppleScript), then paste in the following: on run argv tell application "Audio MIDI Setup" to activate tell application "System Events" to tell process "Audio MIDI Setup" try click menu item "Show MIDI Studio" of menu 1 of menu bar item "Window" of menu bar 1 end try delay 0.2 click menu item "Open Bluetooth Configuration…" of menu 1 of menu bar item "MIDI Studio" of menu bar 1 end tell end run This will take you to the midi bluetooth connection screen. I don't have any bluetooth midi devices, so can't actually see a connect button. For a bit of an explanation of the above script, it opens the Audio Midi setup, then clicks the "Show Midi Studio" item in the menu. This is wrapped in a try block because the menu item is "Hide Midi Studio" if it's already showing. The following delay allows time for this window to show, and the new menu item of "Midi Studio" to be added to the top of macOS. Finally, click the "Open Bluetooth Configuration…" button of the Midi Studio menu. Hope this helps, Andrew
  22. Hmm - this is happening because you likely have the option to show the latest query again: ... which is automatically running the workflow again when you re-show Alfred. The popup you see was never really intended to be seen unless there was a really bad issue, and now that php is missing, this "really bad issue" is actually happening. I am in the process of working through the best solution to this which should also prevent you from getting blocked by this dialog.
  23. Alfred needs read/write access to a local (static) location on your Mac to be able to correctly sync the files. If the location you've set is transient or remote, Alfred may be unable to persist or read preferences. An example of this is setting to iCloud drive (or the Documents folder with macOS configured to keep documents in the cloud), and macOS then "optimising" your storage by removing all of Alfred's configuration files from your local Mac, and making them Cloud only. If you're having issues, the best option is to quit Alfred then make sure the latest copy of Alfred.alfredpreferences is back in the default location of: ~/Library/Application Support/Alfred/Alfred.alfredpreferences then delete the following file, which is where Alfred stores the location of the above package: ~/Library/Application Support/Alfred/prefs.json Cheers, Andrew
  24. Alfred requires the underlying metadata index for any file based search, including apps. This index provides Alfred (and other apps / macOS features) with much more information than simply file search, such as context, type and usage information, so I would recommend against disabling it, if this is what your question was about. Cheers, Andrew
  • Create New...