Did I wake up on the wrong side of the bed?
My New Year’s resolution for 2013 was to learn Vim. I was so new to Vim that I did not even know how to join lines properly. However, I was diligent, patient, and stubborn enough to stick at it. It didn’t take long for me to fall in love. I even ended up writing a plugin for Vim that got so popular that I was writing VimL as a second job.
Sounds like I’m pretty happy with Vim (and I am), so why am I trying Emacs?
Curiosity is a major reason. But more I think the philosophy of Emacs fits my personality better. The Vim community is very much divided into two camps: the text editor people, and the people who try to turn Vim into an IDE. I am in the latter. My vim distribution has over 90 plugins. While I haven’t yet run into Vim’s limitations of trying to use it this way, I can already see the walls coming up…
But here’s the thing, I’m addicted to modal editing, not Vim. It just so happens that Vim is the best implementation of modal editing, but Emacs has something that does a pretty damn good job too! And it’s none other than evil-mode.
With evil-mode, it’s finally possible to have the best of both worlds. The power of modal editing with the near limitless extensibility of Emacs.
And as an added bonus I can finally have an excuse to learn a Lisp dialect. I discovered with Vim that customizing your editor is an incredible catalyst for learning a new language. It wasn’t my intention to memorize a sizable portion of the VimL standard library when I started using Vim, but it happened anyway once I started tweaking and customizing…
My goal is that by the end of this post you’ll have a working Emacs installation with Vim keybindings out of the box.
Back to Basics
The best way to learn is to start from scratch. And so I did exactly that starting with the built-in tutorial
C-h t. While the purpose of this blog post is to get modal editing working in Emacs, you’re not going to be able to make everything modal, so you still need to know basic commands to navigate around.
Things you need to know
There are a couple important Emacs keys that you should know.
C-gis the universal “get me out of here” key, equivalent to
C-his the “help” prefix.
C-h C-hwill show you all possible options. I’ve found that I use
C-h fvery often, which is used to lookup help for functions.
C-xis a also very important, as it’s the prefix for many common things like saving and finding files.
C-cby convention are used for many things, including the equivalent of
<leader>for user customizations when followed by letters, but also for major and minor mode bindings.
Setting up your “vimrc”
In Emacs, this is the
~/.emacs file. But just like in Vim, where you usually have a
~/.vim directory for various plugins and configuration, Emacs has the
~/.emacs.d directory. As an added bonus,
~/.emacs.d/init.el is automatically loaded, so if you put your dotfiles up on GitHub it’s as simple as cloning it to
What’s with the (((())))?
Going through the documentation is one thing, but making the first change to your
~/.emacs.d/init.el file is daunting, at least for me it was. While Vim also has its own scripting language, VimL, it is much more newbie friendly.
How do you turn on line numbers? You add
set number to your vimrc. It’s simple, straightforward, and obvious. You don’t even know you’re scripting in Vim; it just looks like a configuration file at this point. How do you do that in Emacs? First you search on Google, which links you to this EmacsWiki article. If that doesn’t scare you from using Emacs I don’t know what will.
The short answer is, you add
(global-linum-mode t) to your
init.el file. Right off the bat the questions would be, is that a variable, a function? What is
Configuring Emacs throws you into Lisp from the get go, so what you want to do is actually read Introduction to Programming in Emacs Lisp.
You’re going to be seeing a lot of Lisp, so let’s summarize the basics:
setwill set a variable, but you will rarely see this.
setqis very frequently seen. The q stands for quote, which will sidetrack you to understanding what a quote is.
setq-defaultsets a variable if it’s not already set/overridden.
defundefines a function.
-pby convention is added to functions that return true or false (the p stands for predicate).
Now that things are a bit more readable, we can begin setting up our configuration to get evil-mode installed.
Emacs 24 comes with built-in package management. The default GNU repository doesn’t really have many packages, but luckily there’s a community driven repository named MELPA where up to date packages are built directly from GitHub.
So, let’s add the MELPA into our
;;; this loads the package manager (require 'package) ;;; here there's a variable named package-archives, and we are adding the MELPA repository to it (add-to-list 'package-archives '("melpa" . "http://melpa.milkbox.net/packages/") t) ;;; loads packages and activates them (package-initialize)
OK, straightforward so far.
Next up is the all important
M-x binding (on modern keyboards M is the Alt key). This is sort of like Vim’s
: where you can type commands. Here we are going to do a
M-x package-refresh-contents RET. In Emacs,
RET is the convention for
<CR>. This will refresh the repository of available packages. And finally,
M-x package-install RET evil RET.
And now it’s installed!
It’s not enabled by default, so we need to append the following lines to our
(require 'evil) (evil-mode t)
C-x C-c to quit Emacs and restart it. If you’re feeling adventurous you can use
M-x eval-buffer RET instead.
Congratulations! You have a working Emacs installation with Vim modal editing!
You may notice that in addition to
C-x that I mentioned earlier,
C-u will not scroll up half a page as you would expect. This is because by default this is mapped to the Emacs
universal-argument function, which is used for repeating. You can of course customize all of this, but I’ll let you take it from here…
And so there you have it!
git clone https://github.com/bling/emacs-evil-bootstrap.git ~/.emacs.d will automate this entire blog post and let you try Vim in Emacs in 10-20 seconds.