No mojave on this machine

I bought this MacBook Pro in July 2011. It is a 13" machine, to which I added 16gb of ram from the start.

A few months ago I removed the hard disk that was getting really old and seemed to have issues, and put an SSD drive instead. The speed bump was immediately noticeable and it really felt like this machine was getting a second life.

Now I had one issue left. Battery life.

The original battery served me well for 7 years. After more than 1300 cycles, the capacity was down to about 50% of the original battery, which meant 2h30 of autonomy at best (unless you cut wifi and a number of services that run in the background). I started putting a recharger in my bag a few weeks ago but that was not a really satisfying situation.

This week, I decided to get a new battery. The difficult part is to identify a maker that sells good products, at a reasonable price. I eventually found a seemingly good product for about ¥8000 and installed it right away.

It looks like the battery sensors needed some time to get used to the new data. At first they were struggling to reconcile the legacy data with the new battery performance. Eventually I am at a point where I get at least 5 hours on a charge. That's a huge improvement since I'm seldom far from a power cord for more than 5 hours, and I usually don't work on the machine for that much time in a row.

So, now that my machine is almost like new (except for the bumps and scratches on the aluminium cover, for the keyboard keys that seem to have taken a hit from my nails after so many years, and for the screen that seems to have some imprinted key shapes on it that I can't remove), I was thinking that a software upgrade was in order. But I knew from when mojave was announced that High Sierra would be the last macos version I could install on that machine.

I think it's the first time my work machine is too old to support the latest version of macos. But after the hardware upgrades, and the fact that 16gb makes it run extremely smoothly even for a 7 years old machine, I don't feel like I need a new machine.

I heard stories about the touch bar and about the keyboard on the new MBPs. I wouldn't want to spend money on Apple hardware if I were not sure such issues were solved. Also, if I were to buy a new laptop, it would probably be a super light and thin machine. So unless something bad happens, I guess I'll wait for a few more years, when the applications I use require frameworks that do not support this High Sierra machine anymore. Then, I'll buy the equivalent of what the current Mac Book is. A super tight (is "tight" a contraction of "thin" and "light"?) machine, with nice specs (and they will feel especially nice after having worked on this MBP for about 10 years).

Easily launch scripts from Spotlight

I've been advertising AppleScript a lot here. Automating a task is something, but easy access to that automation is quite important too.

Since I try to stick to Apple solutions and free software* I prefer using Spotlight instead of all the smart launchers that we have for macOS.

What I do is that I call my script names that are easy to call first in Spotlight. A few screenshots speak louder than words so here we are:

The series that start with ">" usually is scripts that I use to open something.

See how just typing ">" suggests ">BB". That ">BB" is what I use to open the files selected in Finder with BBEdit.

The one below is ">Tedit", short for "TextEdit" and opens selected files in TextEdit, etc.

If I type "c" after ">", I get the following list of choices. ">command" is to launch an arbitrary command in Terminal, ">Capture" is to use org capture in Emacs (see here and here for more information) and ">cd" just opens a Terminal tab on the front Finder window, or selected Finder folder.

When I use "<" to initiate the search, I get a different list. That series is for scripts that usually act by themselves. "<text file" creates a text file in the front Finder window and proposes to open it in BBEdit for editing, "<facturation" is an invoicing script for the job selected in Finder, "<job" is a job managing script that creates a job hierarchy in Finder based on a mail, along with an event in calendar, and then "<xls2tmx" is a TMX converter for multicolumn Excel reference data (I'll publish it when it's more polished, but creating XML data with AppleScript is documented here).

I have a few more scripts (a dozen) that I routinely call with Spotlight, which I find totally sufficient for my needs.

As you know, hitting Command+Enter when you have a selection in Spotlight is a way to reveal that selection in the Finder if it is available. So when I want to edit a script, I start by calling it in Spotlight, I hit Command+Enter when it is selected and then I call ">SEditor" (Script Editor) or ">debugger" (Script Debugger) on the selection, to open it with the appropriate application...

Ok, I do have BBEdit, Microsoft Office and Illustrator... And maybe a few others...