Next: Arrow keys Prev: Emacs editing modes Up: Top
Like vi, Evi will source your `.exrc' or `~/.exrc' file, and/or your
`EXINIT' environment variable. If your startup runs into problems, let
me know - you shouldn't have to change your vi initialization stuff to
make Evi happy.
If you wish to use some Evi extensions in your startup, but still
need to use vi, place these in `.exrc.evi', `~/.exrc.evi' or `EVIINIT'
so that vi won't gag on them.
Emacs lisp startup code for evi, such at that suggested in the
previous sections, can be placed in either `.evirc' or `~/.evirc'.
And you can, of course, hack away at the the Evi source code if you
want something not easily addressed by the above methods. If you feel
what you've done would be generally useful, please email it to me, or
One particular customization, not covered elsewhere, is how Evi
handles the current directory. By default it behaves like vi - you
have one global current directory, which you change using `:cd' (also
see `:pushd', and friends described below). Alternately, you may like
the emacs behaviour better, which is that each buffer has its own idea
of the current directory, and by default that directory is the directory
that the file for that buffer resides in. In this mode, you can also
change the current directory using `:cd', but that will only affect the
current buffer. To get this behaviour, place the following in your
(setq evi-global-directory nil)
Another customization you might like to make is to alter the
behaviour of `ZZ'. By default it is bound to `:Wq!', which quietly
writes all modified files and exits. If, however, you would like to be
asked about each modified buffer before it is saved in order to avoid
accidently saving a file you didn't want saved, map `ZZ' to `:Wq':
map ZZ :Wq\n
automatically generated by info2www