Learn Vim at your own pace with my self-study Core Vim Course.

Learn more

Learn Vim at your own pace with my self-study Core Vim Course.

Oil and vinegar - split windows and the project drawer

Do you avoid using Vim’s split windows because they’re confusing? That might be a problem of your own devising. If you’ve bolted a project drawer onto Vim, then you’ve added unnecessary complexity to Vim’s otherwise minimal interface. Split windows and the project drawer go together like oil and vinegar. I don’t mean to say that you can combine them to create a delicious salad dressing. I mean that they don’t mix well!

The project drawer (you’ve already met)

Picture your typical GUI based text editing environment. The standard interface usually features a file explorer in a sidebar. It’s sometimes called the project drawer, because it can slide out of view when it’s not being used. I’m sure you know what I’m talking about, but here’s a screenshot just in case:

Screenshot of TextMate's project drawer

I’m not a big fan of file explorers. I usually find it quicker to open files using a fuzzy-file matcher plugin such as cmd-t or ctrl-p for Vim. But I wouldn’t write off the file explorer entirely. It still has its place, particularly during the orientation phase with a new codebase.

The problem with project drawers

Picture this scenario: we’ve got 3 split windows visible at once, and we want to open another file.

Screenshot of 3 split windows with a bolt-on project drawer

If we select a file in the project drawer, which split window will it appear in?

It’s difficult to tell just by looking. The sensible default would be for the new file to open in whichever split window was last active. The most recently touched split window has the focus, so that’s where the new file should open when selected in the project drawer.

It works, but this solution lacks clarity. It’s easy to imagine a scenario where the user mistakenly thinks that window C has the focus, when in fact the focus belongs to window A. Think of the confusion that would be caused when a file selected in the project drawer replaced the contents of window A instead of appearing in window C.

To recover from this mistake in Vim, you could activate window A and switch to the alternate file by pressing <C-^> (:help ctrl-^). Then activate window C, switch back to the project drawer and select the target file. That’s a lot of clean up for a simple mistake. Beware of gumption traps such as this!

An alternative to the project drawer: the split explorer

Here’s the same scenario with the project drawer removed:

Illustration of 3 split windows, with buffers a, b, and c

In this illustration, I’ve shaded window C to indicate that it has the focus. Suppose that we could invoke a command that would draw a file explorer inside of split window C. It might look something like this:

Illustration of 3 split windows with a file explorer in place of c

When we select an item in this file explorer, it would open up the specified file in the same split window:

Illustration of 3 split windows, with buffers a, b, and d

Think of it like this: each split window can either act as a view onto the contents of a file, or it can act as a view onto the contents of a directory. You might even say that each window has a ‘file viewing mode’ (the usual view) and a ‘directory viewing mode’ (the file explorer). I find that it helps to imagine a card-flip transition as the window shifts between file and directory viewing modes.

This model has a distinct advantage over the project drawer: it’s clear which of the split windows will receive the file selected in the explorer. If you were to accidentally activate the file explorer whilst focussed on the wrong window then you would know (and be able to revert) immediately. That leads to fewer errors and less confusion.

More importantly: it makes it really easy to use Vim’s split windows. And that’s a good thing, because Vim’s split window functionality is awesome!

Vim’s split windows are awesome

We can easily divide Vim’s interface into split windows. The <C-w>s command splits the current window horizontally, while the <C-w>v command divides the current window vertically. This figure illustrates a few of the possible results. In each case, the shaded rectangle represents the active window:

illustration showing cell division

When dividing a window in this manner Vim reuses the active buffer in the new window, so you end up with two views onto the same file. I like to think of the process as resembling cell division!

Vim’s split-window feature is really flexible and easy to use. If you’re not making full use of it, you’re missing out! Vimcasts Episode 7 demonstrates how to use Vim’s split windows.

NerdTree is a project drawer, netrw is a split explorer

NerdTree is one of the most popular plugins for Vim. It implements a file explorer using a model that resembles the project drawer. There’s a less well-known file explorer plugin for Vim called netrw. It’s not quite as polished as NerdTree, but it gets one thing right: it uses the split explorer model.

If you’re a NerdTree user and curious to try this approach, you’ve got a couple of options. You could add this to your vimrc, which modifies NerdTree to make it use the split explorer model:

let NERDTreeHijackNetrw=1

Or you could uninstall NerdTree and use the netrw plugin instead. The netrw plugin is usually included in the Vim distribution by default, so you don’t need to do anything to install it. For more details, refer to episode 15 of Vimcasts: The File Explorer

Like oil and vinegar, the project drawer and split windows don’t mix

The project drawer works well in an interface where you can only view one file at a time, but the concept does not translate to the split-window interface. When working with multiple files in split windows, the split explorer is a better fit.

The illustrations in this blog post are adapted from Practical Vim. For more discussion, please refer to Tip 43 Explore the file system with netrw and Tip 39: Divide your workspace into split windows.


Level-up your Vim


Boost your productivity with a Vim training class. Join a public class, or book a private session for your team.

Drew hosted a private Vim session for the shopify team that was one of the best workshops I have ever attended.

John Duff, Director of Engineering at Shopify


Make yourself a faster and more efficient developer with the help of these publications, including Practical Vim (Pragmatic Bookshelf 2012), which has over 50 five-star reviews on Amazon.

After reading it, I've switched to vim as my default editor on a daily basis with no regrets. ★★★★★

Javier Collado

Learn to use Vim efficiently in your Ruby projects

In association with thoughtbot, one of the most well respected Rails consultancies in the world, I've produced a series of screencasts on how to make navigating your Ruby projects with Vim ultra-efficient. Along the way, you’ll also learn how to make Ruby blocks a first-class text object in Vim. This lets you edit Ruby code at a higher level of abstraction. Available to buy from thoughtbot..