Skip to main content

OS X: Aquamacs

I am a die hard Vim fanatic, as many of you know. I actually like modal editing. However, in the Erlang world, everyone seems to use Emacs, and the Erlang mode for Emacs is quite advanced. The practical thing to do is to use Emacs for Erlang and Vim (since I like it so much) for everything else. The only problem is that every time I learn something in Emacs, I tend to forget something in Vim ;) Yes, my brain is that small!

Fortunately, Bob Ippolito introduced me to Aquamacs, an easy-to-use, Mac-style Emacs for Mac OS X. Being a GUI guy, I was immediately pleased to see the nice Cocoa interface. (This is one thing I always liked about Vim, there's a native version of GVim for each operating system.) However, what's even better is that they've gone to great pains to make Emacs feel natural for OS X users. All the normal Apple shortcuts work. Even though I've taken the Emacs tutorial a quarter dozen times, using Aquamacs, I felt more productive almost instantly. The menus also helped quite a bit. I like the configuration system too; I figured out how to turn off backups without having to read the manual.

All in all, I'm not planning on giving up Vim, but using Aquamacs is making me a much happier Erlang coder.

Comments

Anonymous said…
Don't forget M-x viper-mode - that one's for you VI(M) guys!
Anonymous said…
I'm surprised. I briefly tried Aquamacs, spent some time trying to disable its "enhancements" (boatloads of frames, color theming, CUA keys, ...), then gave up and went back to standard GNU Emacs from CVS. I would figure that a vi person would prefer normal emacs to a dumbed-down offshoot.
Bob Van Zant said…
Does that mean you're working with Ippolito on a daily basis now? Somewhat related to that question: I had a recruiter working on behalf of Foxmarks email me yesterday.
jjinux said…
> I would figure that a vi person would prefer normal emacs to a dumbed-down offshoot.

Well, I'm already a Vim expert, and I'm not all that interested in becoming an Emacs expert. Aquamacs lets me be productive in Emacs so that I can code in Erlang without needing to learn quite so much.
jjinux said…
> Does that mean you're working with Ippolito on a daily basis now?

Yep.

> Somewhat related to that question: I had a recruiter working on behalf of Foxmarks email me yesterday.

heheh

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p