@copying
Copyright @copyright{} 1995, 1996, 1997, 2001, 2002, 2003, 2004,
-2005, 2006, 2007 Free Software Foundation, Inc.
+2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
+under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
-Invariant Sections, with the Front-Cover texts being ``A GNU
-Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
-license is included in the section entitled ``GNU Free Documentation
-License'' in the Emacs manual.
-
-(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
-this GNU Manual, like GNU software. Copies published by the Free
-Software Foundation raise funds for GNU development.''
-
-This document is part of a collection distributed under the GNU Free
-Documentation License. If you want to distribute this document
-separately from the collection, you can do so by adding a copy of the
-license to the document, as described in section 6 of the license.
+Invariant Sections, with the Front-Cover texts being ``A GNU Manual'',
+and with the Back-Cover Texts as in (a) below. A copy of the license
+is included in the section entitled ``GNU Free Documentation License''.
+
+(a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
+modify this GNU manual. Buying copies from the FSF supports it in
+developing GNU and promoting software freedom.''
@end quotation
@end copying
@titlepage
@title Viper Is a Package for Emacs Rebels
@subtitle a Vi emulator for Emacs
-@subtitle April 2007, Viper Version 3.13.1
+@subtitle November 2008, Viper Version 3.11.2
@author Michael Kifer (Viper)
@author Aamod Sane (VIP 4.4)
@insertcopying
@end titlepage
+@contents
+
@ifnottex
@node Top, Overview,, (DIR)
@code{kifer@@cs.stonybrook.edu} is the current address for Viper bug reports.
Please use the Ex command @kbd{:submitReport} for this purpose.@refill
+@insertcopying
@end ifnottex
@menu
Meta keys (usually on each side of the space bar). On a dumb terminal, Viper
sets this variable to @code{twice}, which is almost like @code{nil}, except
that double @key{ESC} beeps. This, too, lets @key{ESC} to be used as a Meta.
-@item viper-ESC-keyseq-timeout 200 on tty, 0 on windowing display
-Escape key sequences separated by this much delay (in milliseconds) are
-interpreted as command, ignoring the special meaning of @key{ESC} in
-VI. The default is suitable for most terminals. However, if your terminal
-is extremely slow, you might want to increase this slightly. You will know
-if your terminal is slow if the @key{ESC} key sequences emitted by the
-arrow keys are interpreted as separately typed characters (and thus the
-arrow keys won't work). Making this value too large will slow you down, so
-exercise restraint.
@item viper-fast-keyseq-timeout 200
Key sequences separated by this many milliseconds are treated as Vi-style
keyboard macros. If the key sequence is defined as such a macro, it will be
Setting this variable too high may slow down your typing. Setting it too
low may make it hard to type macros quickly enough.
-@item viper-translate-all-ESC-keysequences @code{t} on tty, @code{nil} on windowing display
-Normally, Viper lets Emacs translate only those ESC key sequences that are
-defined in the low-level @code{input-decode-map}, @code{key-translation-map}
-or @code{function-key-map}, such as those
-emitted by the arrow and function keys. Other sequences, e.g., @kbd{\\e/}, are
-treated as @kbd{ESC} command followed by a @kbd{/}. This is good for people
-who type fast and tend to hit other characters right after they hit
-ESC. Other people like Emacs to translate @kbd{ESC} sequences all the time.
-The default is to translate all sequences only when using a dumb terminal.
-This permits you to use @kbd{ESC} as a meta key in insert mode. For instance,
-hitting @kbd{ESC x} fast would have the effect of typing @kbd{M-x}.
-If your dumb terminal is not so dumb and understands the meta key, then you
-probably will be better off setting this variable to @code{nil}. Try and see which
-way suits you best.
@item viper-ex-style-motion t
Set this to @code{nil}, if you want @kbd{l,h} to cross
lines, etc. @xref{Movement and Markers}, for more info.
In Insert state, this key acts as a temporary escape to Vi state, i.e., it
will set Viper up so that the very next command will be executed as if it
were typed in Vi state.
-@item viper-ESC-key "\e"
-Specifies the key used to escape from Insert/Replace states to Vi.
-Must be set in @file{.viper}. This variable cannot be
-changed interactively after Viper is loaded.
@item viper-buffer-search-char nil
Key used for buffer search. @xref{Viper Specials}, for details.
@item viper-surrounding-word-function 'viper-surrounding-word
@vindex @code{viper-vi-style-in-minibuffer}
@vindex @code{viper-no-multiple-ESC}
@vindex @code{viper-always}
-@vindex @code{viper-ESC-keyseq-timeout}
@vindex @code{viper-fast-keyseq-timeout}
@vindex @code{viper-ex-style-motion}
@vindex @code{viper-ex-style-editing}
@vindex @code{viper-replace-region-start-symbol}
@vindex @code{viper-allow-multiline-replace-regions}
@vindex @code{viper-toggle-key}
-@vindex @code{viper-ESC-key}
@vindex @code{viper-buffer-search-char}
@vindex @code{viper-surrounding-word-function}
@vindex @code{viper-vi-state-hook}
@printindex cp
-@setchapternewpage odd
-@contents
@bye
@ignore