Improves Signposts feature and makes a couple of minor corrections.
log
Supports both continuous and discontinuous selection of log entries, copy their text contents, Signposts, and smart window and file naming.
This first experimental version gets log extracts direct, rather than using the log command tool, and has a SwiftUI front end, but requires macOS 14.6 or later.
Why do some Macs apparently not have Unified log files? Maybe it’s because they’re being deleted by a misguided housekeeping app. Here’s what is going wrong, and what you should do to avoid that.
Introduced with Mac OS X, logs became a good way to diagnose a Mac’s problems, using Console. Then in 2016 it all changed, and not for the benefit of administrators or users.
Tuning your Mac for performance can be a good investment of time. Beware of general benchmarks, though, and develop your own objective measurements. Then identify the rate-limiting step methodically, so you can address that.
macOS logs may only last a few days, or even hours, into the past. Here’s a quick and simple way of browsing the log from weeks, months or even years ago.
Equipping LogUI with controls to get log extracts from arbitrary periods in the past reveals two shortcomings: high memory use, and failure to release that.
Displaying log entries using semantic colour seemed most appropriate using AttributedString, but performs very poorly. The solution is a SwiftUI List view.
Moving away from using the log command tool to obtain log extracts for browsing requires using OSLog. Its API explored and implemented in a demo app.
The Eclectic Light Company 