7 Reasons to choose a VIM editor

I hate it when I just started using VI text Editor! I think this is the most painful and anti-human editor ever designed. But I decided I had to learn it, because if you're using unix,vi everywhere and is the only one that guarantees you can use the editor. In 1998 it was so, but until today VI is still available, in almost every distribution available, VI is basically part of the foundation installation.

I've spent almost 1 months on VI before I learned to use any of the features, but I still don't like it. But then I realized that there was a powerful editor hidden behind this strange appearance. So I insisted on using it and finally found out that once you know what you're doing, it's a fast, incredible editor.

The name "VI" is the abbreviation for "visual visual". When VI appears, the line editor is very common, and it is unusual to be able to display and edit multiple lines at once. Vim, the abbreviation for "VI improved", was originally released in 1991 by Bram Moolenaar, which became the main imitation Vi software and extended the functionality that this powerful editor already has. Vim's powerful regular expressions and ":" Command-line syntax began in line editing and the Telegraph typewriter era.

Vim, with a history of more than 40 years, has plenty of time to develop the volume and complexity of the skills, even the most user can not fully grasp it. Here's a list of some reasons to love Vim:

Color scheme: You may know that Vim has color syntax highlighting. But do you know that you can download hundreds of color schemes? Find something better here.

You no longer need to get your hands off the keyboard or touch the mouse.

VI or VIM exist anywhere, even in the OpenWRT inside also have VI (well, actually is in BusyBox, it is very useful).

Vimscript: You might want to remap a few keys, but do you know that Vim has its own programming language? You can redefine the behavior of your editor or create a language-specific editor extension. (Recently I was customizing Vim for Ansible behavior.) The best entry point for learning this language is to see Steve Losh's famous book, Learnvimscript, the hard one.

Vim has plugins. Use Vundle (which is what I use) or pathogen to manage your plugins to enhance Vim's functionality.

Plugins can integrate Git (or VCS you choose) into Vim.

There are large and active online communities, and if you ask questions about Vim on-line, someone will definitely answer.

The funny thing about the first thing I hated about VI was that over the past 5 years I've been trying to hit the wall with a new editor and always wanted to find something better. I've never hated the other editor like I hated VI, and now I've been using it for 17 years because I can't imagine a better editor. Well, maybe a little better: Try the next Neovim-this is the mainstream of the future. It seems that Brammoolenaar will incorporate most of Neovim into Vim version 8th, which means it will reduce the existing code base by 30%, better code completion, True async, built-in terminals, built-in mouse support, and full compatibility.

If you have a better use of the editor, you can share a bit oh!

7 Reasons to choose a VIM editor