2005-08-06 Michael Kifer <[email protected]>

	* viper-cmd.el (viper-harness-minor-mode,viper-exec-delete,
	viper-exec-yank,viper-put-back): don't display modification msg if in
	the minibuffer.

	* viper-init.el (viper-replace-overlay-cursor-color,
	viper-insert-state-cursor-color,viper-vi-state-cursor-color): make
	variables frame local.

	* viper-util.el (viper-append-filter-alist): use append instead of
	nconc.

	* viper.el (viper-vi-state-mode-list,viper-emacs-state-mode-list): move
	help-mode and completion-list-mode from the first list to the second.
	(viper-mode): docstring.
	(viper-go-away,viper-non-hook-settings): don't localize
	minor-mode-alist in newer emacsen.
	Add advice to set-cursor-color.
	Don't bind "\C-c\\".

1 files changed, 2 insertions, 3 deletions

diff --git a/man/viper.texi b/man/viper.texi
index 0156c4c638..6d05d365f8 100644
--- a/man/viper.texi
+++ b/man/viper.texi
@@ -507,9 +507,8 @@ modes designed for editing files, such as cc-mode or latex-mode, use key
 sequences that begin with @kbd{C-x} and @kbd{C-c}.
 
 There is also a key that lets you temporarily escape to Vi command state
-from Emacs or Insert states: typing @kbd{C-c \} will let you execute a
-single Vi command while staying in Viper's Emacs or Insert state.
-In Insert state, the same can also be achieved by typing @kbd{C-z}.
+from the Insert state: typing @kbd{C-z} will let you execute a
+single Vi command while staying in Viper's Insert state.
 
 
 @node Vi State, Insert State, Emacs State, States in Viper