Vim is a text editor. http://www.vim.org/
My usage pattern
GVim window. Using Vim in it’s own window as opposed to using it inside the terminal prevents unwanted interactions with terminal shortcuts. I use splits, occasionally tabs. Two
:colorschemes I use, depending on the light conditions around me are
vim-scripts Debian package).
- Very powerful editing commands – this works well with the dot (
.) command for repetition.
- Highly customizable
- Can save and load the whole layout (open files, tabs, splits) to a file. See
- Supports C well, including showing the warnings and errors inside the editor after you save a file.
- Ability to record and play macros.
- Many useful plugins, including the one that displays the git branch. The the bottom right part of the screenshot.
- Remote files editing.
- Vim is not an IDE. Don’t expect features such as refactoring.
- I haven’t found the perfect mechanism for navigation between files in a project. The
Ctrl-Pplugin is somewhat helpful.
:BufExploreralso helps. Still doesn’t feel 100% right.
Using Vim in a terminal with tmux
As I mentioned, I don’t usually use Vim this way but some people seem to be very happy to use the terminal+tmux+vim combo.
Nice video about using Vim with tmux: https://www.youtube.com/watch?v=5r6yzFEXajQ
Why not Emacs?
Vim and Emacs are the two best editors I’ve seen. I don’t think either one is better. They are just very different. I have tried Emacs several times. Last time lasted several months. Each time it just did not feel right for me.