I’ve released a new command-line tool called AEQuery. It queries scriptable macOS applications using XPath-like expressions, translating them directly into Apple Events.
The short version: you describe what you want using a slash-delimited path, and AEQuery resolves the SDEF terminology, constructs the Apple Events, and returns the results as JSON.
[…]
The code is on GitHub. There’s also a discussion thread on MacScripter if you’ve got questions or feedback.
Previously:
Time Machine had happily gone that long without backing up or warning me that it had no backup storage. […] I think this results from Time Machine’s set and forget trait, and its widespread use by laptop Macs that are often disconnected from their backup storage.
[…]
If you do just set it and forget it, you will come to regret it.
Today, after a minor disaster with my Obsidian vault, I decided to restore from Time Machine, and… I realized that it had silently broken across both my Tahoe machines.
[…]
It just stopped doing backups, silently. No error messages, no notifications, nothing. Just no backups for around two months.
[…]
After some research, I found out that the issue is with Apple’s unilateral decision to change their SMB defaults (without apparently notifying anyone), and came across a few possible fixes.
Previously:
Using the
logcommand line tool doesn’t require root privileges or require admin authorization, but it needs to be run by a user with admin rights.[…]
What this does is create a
sudoconfiguration which allows all members of thestaffgroup on the Mac, which is a group that has all local users on the Mac as members, to run thelogcommand line tool with root privileges. This removes the need for the account to have admin rights and enables accounts with only standard rights to use thelogcommand line tool to get information from the unified system log on that Mac.
The first bug report, FB21850924, covers a terrible memory leak in SwiftUI’s Table view, a feature our program uses a lot. […] Despite the rapid updates to the data, the sample program only keeps 1000 records in a deque, so the memory usage should bounded. Strangely, switching to another view triggers Swift to reclaim much of the memory.
[…]
The second bug report, FB21860141, covers SwiftUI Table view’s performance degrading quickly. […] Like the memory issue, simply switching to another view or, in this case, (strangely again) even just changing the window size resolves the problem.
Previously:
