On save, I noticed that the image’s extension was .jpeg rather than what I thought was the usual .jpg. As both of my other Macs save with the .jpg extension, I figured something was messed up on the iMac. So I (of course) tweeted about the issue. A while later, Shawn King replied with this seemingly odd suggestion:
So I tried it, and sure enough, changing the screen capture file format via defaults write com.apple.screencapture type jpg and then restarting the SystemUIServer with killall SystemUIServer changed my default JPEG extension in every app to .jpg.
What’s really strange is that I then switched the screenshot format back to png, and the .jpg extension remained. I even went so far as to delete the pref (defaults delete com.apple.screencapture), and still, the extension remains .jpg. So whatever change occurred when switching the default screenshot format, it appears to be permanent.
I tried the same trick for the .tiff extension (which I rarely use, so it doesn’t bother me as much), and it sort of worked: Captured screenshots got a .tif extension, but images saved from apps still got the four-letter .tiff extension. Weird.
If anyone knows exactly what’s going on with the .jpeg vs. .jpg extension, I’d love to hear the explanation.
Yes, that’s a screen saver running in the background, behind whatever work you’re doing. And if nothing else, it’s a great example of the progress of our CPUs and GPUs since 2002. In the original hint, I noted:
On my G4/733 with the GeForce3, this is simply amazing. The new “flurry” screensaver is running right now on the destop at 1600×1200 in thousands, iTunes is playing, the ink recognition floater is open, and yet the CPU utilization is averaging at or below 50% of thereabouts
Today, I’m testing it on a 5K iMac (5120×2880) with a second connected 4K (3840×2160) display—a total of 23,040,000 pixels, or 12 times as many pixels as in 2002—with Flurry running on both screens, and the CPU usage is somewhere around 10% to 15%. (Flurry does send the iMac’s fans into a tizzy, though.) Other screen savers are even less intensive, and don’t send my iMac’s fans into high gear.
I can’t imagine actually working this way for very long, but it is kind of interesting. Here’s how to start (and more importantly, perhaps, stop) a background screen saver.
Between Many Tricks and this blog, I spend a lot of time in browsers. Most of the time, I use Safari, but I do occasionally work in Chrome and Firefox, too—most often to check how a page looks or functions.
I keep my “permanent” bookmarks in Safari, and don’t presently use any sort of cross-browser sync. (I used to use one, but had a lot of trouble with duplicates, so I stopped.)
I wanted a way to open a limited number of URLs in either Safari (if that’s what I was in, or if I wasn’t in a browser), or in the frontmost browser, if that browser were frontmost. I could just create the subset as bookmarks in each browser, but if I wanted to add or remove a page from the list, I’d have to do so multiple times.
In the end, I came up with a set of Keyboard Maestro macros that do exactly what I want. I access my short list of multi-browser URLs via Keyboard Maestro’s pop-up palette, as seen at right.
This appears when I press ⌃1; after that, a single digit opens the desired URL. But how does it know whether to open the URL in Safari or one of the other browsers? It takes one helper macro, then one macro for each URL that I want to open in this manner.
The nice thing about the reinstall is that it’s nothing like a reinstall from days of yore—you’re not starting from scratch, so you won’t have to reinstall everything when done. Apple makes this clear on the support page:
You can install macOS over the same version or earlier version, without removing your data. You don’t need to remove or disable the existing system first.
I say this with crossed fingers, but it seems that this reinstallation has potentially solved my Bluetooth issues. For the last two days, I’ve used my Bluetooth headphones without any static issues at all. In addition, none of my Bluetooth devices have disconnected. There is one comment from slajax on the original article that states this didn’t work for them:
I’ve been having the same issue but with the gen 1 track pad and keyboard. I reinstalled the OS, PRAM etc replaced them with the gen 2 key board and track pad and also had the apple store replace the bluetooth antenna but still having the same issue.
If you’ve reached the breaking point with your macOS Sierra/Bluetooth issues, it might be worth the 30 minutes or so a reinstall takes. But please, if you go this route, make sure you have a good backup first, just in case. And if it works for you, please post in the comments (either here or on the original post), so that others might see, too. I promise to do the same if my now-working Bluetooth turns out to again be not-working Bluetooth.
Now, some may not like the Dock and say it already sucks. But I’m actually referring to a really old hint that ran on Mac OS X 10.0’s release date—March 24, 2001.
The hint explained that the Dock has three minimization modes available; back then, you had no choice of which to use. Now we have a choice between two: Genie (the default) and Scale, selectable on the Dock System Preferences panel. If you’d like to see the hidden third mode, Suck, issue these two commands in Terminal:
What is this speedtest exactly? And what is brew, you may also be wondering? You may also be wondering why, if you have brew, Dave’s command doesn’t work…that’s because it’s actually brew install speedtest_cli…but I’m getting ahead of myself.
speedtest is a command line interface (i.e. Unix app run from Terminal) to the connection speed tests at Speedtest.net—you get the results without the fancy animated graphics. And Brew is “the missing package manager for macOS.” In other words, it’s an app to help you install (and uninstall) other apps.
Here’s how speedtest looks in its default mode—note that I’ve sped things up greatly for the GIF…
Much nicer to me, though, is the simplified version:
No animated dots, just three lines with the results. As you might expect if you read here regularly, I also wrote a Keyboard Maestro macro (of course I did!) that makes it really easy to run the simple version of the test, and does some editing of the output to simplify the display:
If you’d like to install speedtest (and maybe add the macro)—even if you don’t want to install Brew to do so—keep reading…
When you relaunch Safari, you’ll have a (really long) Debug menu on the far right of Safari’s menus. And just why might you want a Debug menu in Safari? Kirk McElhearn offers up one good reason:
Auto-play videos suck. They use bandwidth, and their annoying sounds get in the way when you’re listening to music and open a web page. …
But you can stop auto-play videos from playing on a Mac. If you use Chrome or Firefox, it’s pretty simple, and the plugins below work both on macOS and Windows; if you use Safari, it’s a bit more complex, but it’s not that hard.
In Safari, they key is the Debug menu, as Kirk points out. Go to Media Flags and select (activate) Disallow Inline Video, and that should be the end of auto-playing video. See Kirk’s blog post for ways to do the same in Firefox and Chrome.
Beyond auto-play video, though, there’s lots to geek out about in the Debug menu…
As my collection of macros has grown, and some of those macros have gotten more complex, I’ve been using a few of KM’s features to help keep my macros organized, and make it easier to debug them while I’m working on them. Some of these are obvious, some maybe not so obvious, so I thought I’d share what I’m doing.
I capture a lot of screenshots—both for this blog, and for our Many Tricks’ help files and web pages. Depending on the project, I may need a full screen, a portion of a screen, a window, an object, or some combination of the above. As such, I use a few different ways of capturing screenshots.
First up are the built-in macOS screenshot tools, which you’ll find on the Keyboard System Preferences panel, in the Shortcuts tab:
These four commands let you capture full screens or windows, directly to files or to the clipboard. And, for many users, these may be all you need. If that’s you, great! (You may want to assign some easier-to-type shortcuts, as these—especially the clipboard variants—require some advanced finger gymnastics.)
I use some of these built-in tools, along with a key third-party app, to handle all my image capture needs.
Things I did not know (or perhaps remember): Terminal lets you set the opacity and blur of inactive windows. (Profiles > Text > Background)
…but because I often forget about those things—the ephemeral nature of tweets being what it is—I figured I should post it here, too.
I have no idea when the feature appeared, but I only discovered it on February 27th, when I tweeted about it. You’ll find the window at right in Terminal’s preferences, on the Profiles tab—look in the Text section for a selected window, then click the color tile under Background. Check the box to set opacity and blur for inactive windows, and you’re done.
As I use a dark background in Terminal, I like this feature a lot. I’ve now got it set up to go transparent and fuzzy when inactive—this makes it basically vanish, so the dark background no longer grabs my eye.
At some point, I’ll dig through my virtual machines and figure out when this was added…who knows, maybe it’s been there for forever. In any event, I’m glad I stumbled across it the other day.