Jens Oliver Meiert

Tip: vi Configuration

Post from May 25, 2008 (↻ July 4, 2015), reflecting Jens the .

This and many other posts are also available as a pretty, well-behaved e-book: On Web Development (announcement).

Long story short: It’s easy to modify vi editor’s standard configuration. The most useful changes probably relate to encoding (UTF-8 preferred) and display of line numbers. In order to do that, simply go to your home directory (enter cd), create a file called .exrc unless it already exists (enter vi .exrc, press i or a, paste the following, and save by pressing esc and entering :wq):

:set encoding=utf-8
:set number

That’s it. General interest in vi suggests to have a look at some vi Cheatsheet (PDF). It includes additional :set parameters (you can enter these in command mode, too). Or you get a book about vi—the editor infamously, “unofficially pronounced ‘six’ because of the feeling one gets when using vi that it may be the text editor of the antichrist.”

Update (February 17, 2013)

Here’s my vi configuration, a few years later:

:set encoding=utf-8
:set number
:syntax on

The only change was to enable syntax highlighting.

About the Author

Jens Oliver Meiert, photo of June 20, 2015.

Jens Oliver Meiert is a German author, philosopher, adventurer, artist, and developer. Here on meiert.com he shares—and occasionally generalizes and exaggerates—some of his thoughts and experiences.

If you have any questions or concerns about what he writes, ask him to explain, or share your own position by sending a constructive comment or email. (And, if you think something could be of interest to Jens, recommendations for excellent literature are always welcome.)

Comments (Closed)

  1. On May 25, 2008, 20:36 CEST, Jens Nedal said:

    So there we have another vi user 8)
    In our current work configuration which involves a team of 4 in the programming department, mostly PHP but also some Java and ofcourse the usual standards and accessbility compliant frontend output in HTML, CSS and Javascript/AJAX, 3 of us use vim as our chosen editor in a Windows environment and ofcourse also when working form the console.

    We do have a heavily configured .vimrc with various settings, like some autocompletion for function commentaries, which help keeping the phpdoc tree nice and clean and some other nifty stuff.

    Before i ever used vi i usually tagged along with some editors that had decent highlighting.

    vi is just very powerful and once you get around the “quirk” of only using keyboard commands for everything but marking text with your mouse, it is absolutly worthwhile and i would never move away from it again ever.

  2. On May 27, 2008, 9:42 CEST, Jens Oliver Meiert said:

    Jens, yah, vi is a usability nightmare but still awesome :) Love to see your vim settings!

  3. On June 8, 2008, 18:58 CEST, Martin said:

    Why not use vim, that’s basically the same, just with more features, such as tabbed editing, etc.

    In that case, the configuration file’s called .vimrc.

  4. On June 9, 2008, 19:39 CEST, Jens Oliver Meiert said:

    Martin, please correct me but it seems vi is available on more systems than vim. I like that it’s so wide-spread.

    A small addendum, to use n spaces for indentation (instead of Tab), add the following lines (here using 2 spaces for indentation):

    :set expandtab
    :set tabstop=2

Read More

Have a look at the most popular posts, possibly including:

Or maybe say hi on Google+, Twitter, or LinkedIn?

Looking for a way to comment? Comments have been disabled, unfortunately.

Found a mistake? Reward! Email me, jens@meiert.com.

You are here: HomeArchive2008 → Tip: vi Configuration

Last update: July 4, 2015.

“To change the world for the better, you must begin by changing your own life.”