Updated and republished for macOS 10.14.2; skip it unless you really really care about all the macOS releases. Originally published on November 14th, 2005.
Below the break is a table showing all major releases of macOS (previously Mac OS X) from the public beta through the latest public version, which is macOS 10.14.2, as of December 5th, 2018—the 119th release in total.
Note: Click the ⓘ symbol to read Apple’s release notes for a given update.
Note: Revised on December 4, 2018 with a much better implementation of the pop-up palette, and some changes in timing and mouse movement.
One of the “problems” with Keyboard Maestro is that it’s so useful I use it a lot, leading to a large collection of macros. Due to the number of macros, sometimes when I want to add a new shortcut, I can’t remember if I’ve used that shortcut before or not. Today’s tip comes in two flavors to address that problem: Simple and Complex.
The Simple solution
Short of just trying the shortcut, there’s a way to check from within Keyboard Maestro itself: Type the macro’s activation keys into the search box, as seen in the box at right.
You can’t do this by pressing the actual shortcut keys—you have to type their character representations. You can do this with the “Show Emoji & Symbols” option under the flag icon in the menu bar, if you’ve enabled it in the Keyboard System Preferences panel. But finding those few special keys (if you even know how to search for them) is a pain.
Technically, you could also use the pop-up character palette macro I wrote, except there’s an issue: When the palette activates, it deactivates the search box, so the characters don’t make it there. It’s also overkill for this task, because there are characters that wouldn’t be part of keyboard shortcuts, and you’d never need the HTML codes, just the characters.
So I wrote what wound up being a set of new macros that make searching for assigned keyboard shortcuts much easier.
I recently purchased a new 2018 13″ MacBook Air—my first new Mac laptop in over five years. My hope is that this machine can replace two aging laptops: A 2013 13″ Retina MacBook Pro (I use this when I want more “power” or screen resolution) and a 2012 11″ MacBook Air (I use this when I want portability).
Reviews of this machine are all over the net, so I’m not even going to attempt a full review. If you want an in-depth review of the machine, go read Six Colors’ review, or The Verge’s review or Wired’s review…or just start with Macrumors’ round-up of reviews and go from there.
Instead of a full review, I’ll provide some brief thoughts on the machine, then move on to my main focus: The performance changes in Apple’s smallest laptops from 2012 to today, based on comparisons between my three machines. I was interested in how this would turn out, as the two older Macs are both Core i7 CPUs, versus the Core i5 in the new Air. There’s lots out there to read about how the 2018 Air compares to other current machines, or semi-new machines…but I thought it might be interesting to see how performance has changed in five-plus years.
But first, my thoughts on the new Air…
Note: This was originally published in 2015; I’ve updated it with a minor change required for Mojave, and clarified a bit of the text.
macOS includes—and enables by default—translucency, which gives you ‘wonderful’ effects such as this in Calculator:
This is just one example; lots of other apps (Mail and Messages, to name two) contain panes that become grossly distorted by background color bleed-through. I’m not sure who at Apple (Marketing?) thinks this feature is good for productivity , but I find it completely distracting.
As a result, I turn off translucency on every Mac I own. You can do so yourself in System Preferences > Universal Access > Display. Just check the Reduce transparency* box, and you won’t get any more bleed-through. (You’ll also get a solid Dock, and perhaps the world’s ugliest Command-Tab task switcher. Such is the cost of usability.)
* It’s ridiculous that Apple calls this transparency, which is defined as “the condition of being transparent,” and being transparent means being see-through, clear, invisible, etc. This is clearly translucency, or “allowing light, but not detailed images, to pass through.” But I digress…
However, when writing for Many Tricks or Macworld, I often need to take screenshots. And because most users won’t disable translucency, I prefer to take those screenshots with translucency enabled, so that they’re closer to what most users might see. That means a trip through System Preferences to toggle the checkbox, which gets annoying after the second or third time you’ve done it.
There had to be an easier way—and after some missteps, I eventually found it.
I know, clickbait headline, but really, it’s how I’ve felt since the release of the iPhone X, and still feel today. And no, this isn’t about switching to Android. It’s about not buying a newly-designed iPhone. Why not? Two reasons…
The notch adds nothing to the iOS experience, but takes away much. Those stupid ears grab my eyes every time I see them, and there’s no way to avoid them, save never using anything but an all-black screen. When not in an app, they show status items on a black background, which is fine…as long as your iPhone’s wallpaper is also black.
But once you’re in an app, you’re in Notchville…
This morning, I launched the DirecTV app on my iPhone (connected to my home network via wifi).
On launch, I saw a login screen that looked slightly different than usual; the app had been updated recently, so I assumed it was the new login screen. But when I entered my user name and password (on the first attempt), I saw the screen to the right…
At this point, alarm bells went off. Not just because it was my first attempted login, but also due to the grammar of that last sentence:
“Please, contact AT&T operator.”
That’s wrong in many ways—and there’s no provided method for contacting an AT&T operator. I now believed I had been scammed: Somehow, a fake login page was injected where the app would normally display its login screen. As soon as I pressed Enter after entering my password, I’m sure my username and password were sent off to some server somewhere.
I immediately opened the DirecTV web site on my Mac, logged in (using my supposedly-locked account and current password), and changed my password. That all worked, and I received the email stating I’d changed my password, so I’m pretty sure my account is fine. (And I use unique passwords for each service, so the one that was probably compromised is useless to the hackers.)
But the bigger question here is what happened and how did it happen?
I occasionally need to help one of our customers get the bundle identifier for a given app, for some purpose with one of our apps. While the task isn’t complicated—the value is stored in a file named Info.plist within each app bundle—it’s not something that’s necessarily easy to explain to someone who doesn’t have a lot of Mac experience.
I figured there must be a less-complicated solution, and I was right, though it’s probably higher on the geek factor. After some searching, I found this thread at Super User, which offers a number of solutions. The simplest—and always working, in my experience—was the very first one: Open Terminal and run this command:
osascript -e 'id of app "Name of App"'
The "Name of App" is replaced with the name of the app as it appears when hovering over its Dock icon. For Excel, for example, it’d be:
osascript -e 'id of app "Microsoft Excel"'
Run that command, and it returns com.microsoft.Excel, which is just what I need—I just have the customer copy the output and email it back to me.
For those not aware, I have something of an addiction to portable power packs—with two kids and who knows how many devices, it seems someone somewhere is always out of power.
For the last few weeks, I’ve been testing an addition to our stable of such products: Olala’s $32 10,000mAh Power Bank.1I received the Power Bank at a greatly reduced cost, but my review is based solely on its performance and my impressions of its build quality.
This shiny piano black unit looks great (though that shiny finish is a fingerprint magnet), and its smooth surface means it easily slides into a pocket in a backpack. Four blue LEDs let you know how much juice you have left. Unlike some battery packs, this one is Apple MFi Certified, meaning Olala has gone through the necessary steps to certify that their device meets Apple’s standards. (You can search for MFi certified devices in case you’re ever curious about a given accessory developer.)
A fair number of my apps are still 32-bit—see how many you still have—though many I don’t really care about all that much. But there’s one suite of apps that I use every day, usually multiple times a day: Fujitsu’s ScanSnap apps. This is the software bundled with the ScanSnap ix500 scanner.
While Fujitsu has been good about updating their software in the past, I was a bit concerned about the upcoming 64-bit transition. So I both tweeted at them and sent them an email. I haven’t seen a reply on Twitter, but a (clearly form letter) reply to my email is at least somewhat encouraging:
There is no problem in the behavior of the application or the OS concerned. The message is only inform that the application needs to be modified for compatibility with next-generation macOS (which should be available near the end of the year). PFU is going to resolve this, but the resolution date is not set yet. In the meantime, please continue using the latest version of the software available.
This blurb was obviously prepared as a response to those complaining about the new 32-bit warning dialog in macOS 10.13.4, but it does seem to address the longer-term question: Fujitsu is planning to “resolve this,” which hopefully implies 64-bit versions are in our future, though at some not-yet-disclosed date.
There are very few things in my workflow that I couldn’t replace…but replacing my ScanSnap and everything it does for me would be quite difficult. Hopefully we’ll see a 64-bit ScanSnap suite before this fall’s deadline.
The other day while browsing the Mac App Store, I clicked on an app’s web site link, only to be greeted with this lovely “Can’t Find the Server” error message in Safari…
That got me wondering about just how often that happens—how many apps are out there that are still in the store, yet their developers have closed down their work and moved on to other projects? I thought it might be interesting to look at my App Store purchases and see just how many of them had broken web site links in their App Store entries.
Then I thought that as long as I was looking at each of my purchases, I might as well collect some additional data. So I put together a simple FileMaker Pro database with a few fields for each app…
During my spare time over a few days and nights, I went through every entry in my App Store Purchased list (after unhiding some apps that I’d hidden). I installed them (if they weren’t already installed), tried to run them, and completed the above data card for each app.
I then tried to answer some questions about my App Store purchases over the years…
- How many apps have I purchased? 
- How many do I still use? 
- What types of apps do I purchase? [A variety; lots of games]
- How many appear to have no-longer-there developers? 
- How many of the apps are still in the App Store? 
- How recently have those apps been updated? [Check the chart]
If you want more detail than the [bracketed tl;dr notes] provide, keep reading…