GNU Info

(viper)Customization

---

Next: Commands Prev: Improvements over Vi Up: Top

---

Enter node , (file) or (file)node

Customization
*************

   Customization can be done in 2 ways.

   * Elisp code in a `.viper' file in your home directory.  Viper loads
     `.viper' just before it does the binding for mode hooks.  This is
     the recommended method.

   * Elisp code in your `.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.

Rudimentary Changes

Simple constant definitions.

Key Bindings

Enabling Emacs Keys, Rebinding keys, etc.

Packages that Change Keymaps

How to deal with such beasts.

Viper Specials

Special Viper commands.

Vi Macros

How to do Vi style macros.