Tip: vi Configuration
Post from May 25, 2008 (↻ January 2, 2021), filed under Web Development.
This and many other posts are also available as a pretty, well-behaved ebook: On Web Development.
Long story short: It’s easy to modify the 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, 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. If you’re interested in additional options, have a look at a vi cheatsheet (PDF). It includes additional
:set parameters (you can enter these in command mode, too). Or check out 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
This also enables syntax highlighting.
I’m Jens Oliver Meiert, and I’m a web developer (engineering manager) and author. I love trying things, sometimes including philosophy, art, and adventure. Here on meiert.com I share some of my views and experiences.
If you have questions or suggestions about what I write, please leave a comment (if available) or a message.
On May 25, 2008, 20:36 CEST, Jens Nedal said:
So there we have another vi user 😎
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.
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.
Have a look at the most popular posts, possibly including:
Perhaps my most relevant book: CSS Optimization Basics (2018). Writing CSS is a craft. As craftspeople we strive to write high quality CSS. In CSS Optimization Basics I lay out some of the most important aspects of such CSS. Available at Amazon, Google Play Books, and Leanpub.
Looking for a way to comment? Comments have been disabled, unfortunately.