Improvements over Vi
Top
Commands
Customization can be done in 2 ways.
.viper' file in your home directory. Viper
loads `.viper' just before it does the binding for mode
hooks. This is the recommended method.
.emacs' file before and after the (require 'viper) line. This method is not recommended, unless you know what you are
doing. Only two variables, viper-mode and
viper-custom-file-name are supposed to be customized in `.emacs',
prior to loading Viper.
Most of Viper's behavior can be customized via the interactive Emacs user
interface. Choose "Customize" from the menubar, click on "Editing", then on
"Emulations". The customization widget is self-explanatory. Once you are
satisfied with your changes, save them into a file and then include the
contents of that file in the Viper customization repository, `.viper'
(except for viper-mode and viper-custom-file-name, which are
supposed to go into .emacs).
Some advanced customization cannot be accomplished this way, however, and has to be done in Emacs Lisp. For the common cases, examples are provided that you can use directly.
Improvements over Vi
Top
Commands