Skip to main content

Apple: MacBook Manual Surprises

This is a list of things that surprised me while reading the manual for my MacBook:
  • Use two fingers on the touchpad to scroll.

  • It doesn't come with a modem.

  • The lowest model MacBook can burn CDs but not DVDs.

  • Hit F3 (without fn) or F10 (with fn) to use expose.

  • Turn it off if you're not going to use it for a day or two.

  • Putting it to sleep decreases the chances of damaging the hard drive while moving it.

  • Use "fn delete" to delete characters to the right of the cursor.

  • The manual use to say that if you added memory yourself you would void your warranty. It now says that you'll only void your memory if you mess up ;-)

  • Hold down D while booting to use Apple Hardware Test.

  • The printed manual is only in English.


Anonymous said…
One thing that surprised me on my iBook was: Hold down T on bootup for Target Disk Mode. Once you see the yellow firewire symbol on your screen, now your laptop has been transformed into an external firewire disk.

Fastest way to move data between two Macs.
Eddy Mulyono said…
Does this mean you bought a MacBook, JJ?
jjinux said…
Embarrassingly enough, yes. I'm trying to mix things up to recover from burnout. Hence, I'm switching from Linux to Mac, and I'm switching from Vim to Emacs. I feel very strange.
Anonymous said…
I thought you were going to say you bought this for the family and not yourself :-) How much open source crap have you installed already :-P
Alec said…
FWIW, I leave both my work and home macbooks (Original MacbookPro and 12-month old Macbook) in sleep mode all the time. I typically go 2+ weeks between actual reboots.
jjinux said…
> How much open source crap have you installed already :-P

Ah, you know me well ;)

> I leave both my work and home macbooks (Original MacbookPro and 12-month old Macbook) in sleep mode all the time. I typically go 2+ weeks between actual reboots.

Yeah, that's my favorite feature so far. Going from 2 hours of battery life to 5 makes all the difference in the world. I no longer bother with bringing my power adapter with me when I go to the coffee shop or to meet with people.
dm said…
I whimsically clicked on your "Apple" tag and found this post. Interesting contrast with your previous Apple post. What happened to loving the freedom, man?
jjinux said…
I was desperately burnt out, so I started trying a bunch of things to get me over the burnout. I switched from Linux to Mac, Vim to Emacs, and Python to Ruby.

I ended up really disliking Emacs per my post here: I seem to go through an Emacs phase every couple years, and I always en up back with Vim.

I decided I still liked Python more than Ruby, but I was sick of Web development. Hence, my current job is mostly not Web related.

The Mac is nice. It's really the hardware I like best. 5 hours of battery life rules, and suspend works really well. I haven't really started using anything proprietary yet. I'm still all about Vim, zsh, Flock, Python, etc.
jjinux said…
> What happened to loving the freedom, man?

I thought about it a lot, and I explained it here:
bsergean said…
Suspend to RAM works fine on Linux too. This article explain it all.
I just had to add two lines in my xorg.conf to get my lenovo with nvidia hardware to suspend / resume.

But I type this on a MacBook Pro ... I have to say it's a really nice hardware. One thing I really like is the screen, that is probably back-lighted so you can see it's content everywhere even when there is some sun coming in.
jjinux said…
I know; I'm normally a Linux guy. The thing about MacBooks is that suspend works *reliably right out of the box*.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…