Terminal Vim, especially when you want to use high-color colorschemes, is indeed more work to set up. However, you'll find a plethora of articles and tips on the Web. Since you didn't tell your precise problems, just two tips:
- Ensure that the colorscheme supports high-color terminals (some are GVIM-only)
- Use a modern terminal emulator like
gnome-terminal
, and properly set the TERM
variable (i.e. gnome-256color
); this avoids messing with :set t_Co
, which is a hack.
GVIM
Pros
Visually, you gain some additional highlighting capabilities like the undercurl for spelling errors, and the full 24-bit RGB spectrum of colors.
You also have more keys available for mapping (or at least, more keys are straightforward to map without having to delve into key code and terminal issues).
Cons
If your Vim workflow heavily interacts with the shell, i.e. if you execute lots of external :!shell-command
, or :make
, or launch a :shell
from within Vim, only the terminal offers full capabilities; GVIM only has a primitive terminal emulation built-in, so some output may be wrong or is missing highlighting.
I personally do most of my editing in GVIM, but occasionally start Vim in a terminal (e.g. to edit Linux config files or through SSH).