What's changed in 2.5.8b5 (418)

  • The location popup menu now has a "home folder" item. I hope you like that.
  • The Hidden and Trashed columns now use different icons.
  • The "Copy as JSON format" command works again (was broken in a previous beta).
  • Some (mostly internal) changes to the AppleScript support.
  • More bug fixes.

What's changed in 2.5.8b4 (417)

  • Adds more columns to the results: Comments, Hidden state, Trashed state, Container (shows the name of the app or bundle for items inside).
  • We can now find non-empty Comments and Tags by using "matches pattern *"
  • Finding Comments has been fixed so that it works on external and remote volumes as well, seeing exactly what the Finder sees (FAF now parses the .DS_Store file to accomplish that).
  • Scripts can now launch (shell) commands with root permissions.
  • Scripts can now perform their own search and provide that to the other rules for filtering.
  • The local iCloud folder can now be conveniently excluded in the Special Folders window.
  • If FAF doesn't have Full Disk Access, it will now present a helping window with instructions in macOS 13 and later..
  • Several bug fixes and optimizations.

What's changed in 2.5.8b3 (416)

  • New results columns for Comments and Container. Container means that it shows the enclosing package name (e.g. the app name), otherwise the parent folder's name.
  • Improves Comments fetching: Now queries the correct comments from Finder's .DS_Store files instead of relying only on the Extended Attributes (which often don't work on external volumes).
  • Adds basic AppleScript support: You can now start a search and query the results.

What's changed in 2.5.8b2 (415.5)

  • The Show/Hide switches that are at the top of the Results window are now also found in the View menu.
  • Should fix the frequent freezes that happened in v2.5.7. As a nice side effect, the search is now also faster when using computing intensive rules.
  • Fixes the number of found items shown in the Find window - it was sometimes too high when items were also found by Spotlight.
  • Rudimentaty AppleScript support has been implemented. For now, it's good enough to start a search, wait for it to complete and read the paths of all found items. If you like to automate FAF with AppleScript, let me know what you need so that I can prioritize.

What's changed in 2.5.8b1 (414)

  • If Default Folder X is installed, its Favorites menu in FAF's Find window now offers an "All" choice for using all favorite folders as search locations. And if there are multiple Folder Sets configured, each set's favorites and recent folders can be accessed now from the "where" pop-up menu.
  • Fixes a bug where the Services command "FAF: Search folder(s)" picked the wrong location if a file instead of a folder was selected.

What's changed in 2.5.7 (413)

  • No functional changes since 2.5.7b3 other than ending the beta status.

What's changed in 2.5.7b3 (412)

  • Fixes several cases where FAF would sometimes crash.
  • This version is likely getting released soon as v2.5.7 unless new issues arise.

What's changed in 2.5.7b2 (411)

  • New: While holding down the cmd key, you can now reorder the rules in the Find window by dragging the (≡) handle on the left.
  • Fix: The result update correctly again after trashing items.
  • Fix: Search for Extension on Synology works now via Spotlight.
  • Fix: Doesn't erase all preferences any more when using FAF in root mode on latest macOS versions.
  • Fixes issues in "ssh find" (Pro version) when searching for certain special characters.

What's changed in 2.5.7b1 (410)

  • It's now possible to search Time Machine backups on recent macOS versions (these backups are technically APFS snapshots and require FAF to perform extra steps to access them). To search these backups, mount your backup volume and then choose it from the search location popup menu, where it says "(with backups)".
  • Fixes a few reported crashes.

See here for Release Notes for all previous versions.

If you find issues with FAF's translations (Spanish, French, Japanese etc.), you can now suggest corrections online at https://simplelocalize.io/suggestions/?id=8288105bbff249b3b65394b31017e26a.