aboutsummaryrefslogtreecommitdiffstats
path: root/doc/misc/viper.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/misc/viper.texi')
-rw-r--r--doc/misc/viper.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/misc/viper.texi b/doc/misc/viper.texi
index 1f0dffee5b4..86455524b1f 100644
--- a/doc/misc/viper.texi
+++ b/doc/misc/viper.texi
@@ -7,7 +7,7 @@
7@setfilename ../../info/viper 7@setfilename ../../info/viper
8 8
9@copying 9@copying
10Copyright @copyright{} 1995-1997, 2001-2011 Free Software Foundation, Inc. 10Copyright @copyright{} 1995-1997, 2001-2012 Free Software Foundation, Inc.
11 11
12@quotation 12@quotation
13Permission is granted to copy, distribute and/or modify this document 13Permission is granted to copy, distribute and/or modify this document
@@ -687,7 +687,7 @@ Insert state. For instance, Emacs has a @dfn{yank} command, @kbd{C-y},
687which is similar to Vi's @kbd{p}. However, unlike @kbd{p}, @kbd{C-y} can be 687which is similar to Vi's @kbd{p}. However, unlike @kbd{p}, @kbd{C-y} can be
688used in Insert state of Viper. Emacs also has a kill ring where it keeps 688used in Insert state of Viper. Emacs also has a kill ring where it keeps
689pieces of text you deleted while editing buffers. The command @kbd{M-y} is 689pieces of text you deleted while editing buffers. The command @kbd{M-y} is
690used to delete the text previously put back by Emacs' @kbd{C-y} or by Vi's 690used to delete the text previously put back by Emacs's @kbd{C-y} or by Vi's
691@kbd{p} command and reinsert text that was placed on the kill-ring earlier. 691@kbd{p} command and reinsert text that was placed on the kill-ring earlier.
692 692
693This works both in Vi and Insert states. 693This works both in Vi and Insert states.
@@ -1289,7 +1289,7 @@ the following example:
1289The above discussion of the meaning of Viper's words concerns only Viper's 1289The above discussion of the meaning of Viper's words concerns only Viper's
1290movement commands. In regular expressions, words remain the same as in 1290movement commands. In regular expressions, words remain the same as in
1291Emacs. That is, the expressions @code{\w}, @code{\>}, @code{\<}, etc., use 1291Emacs. That is, the expressions @code{\w}, @code{\>}, @code{\<}, etc., use
1292Emacs' idea of what is a word, and they don't look into the value of 1292Emacs's idea of what is a word, and they don't look into the value of
1293variable @code{viper-syntax-preference}. This is because Viper doesn't change 1293variable @code{viper-syntax-preference}. This is because Viper doesn't change
1294syntax tables in fear of upsetting the various major modes that set these 1294syntax tables in fear of upsetting the various major modes that set these
1295tables. 1295tables.
@@ -2504,7 +2504,7 @@ major modes.
2504@item viper-minibuffer-emacs-face 'viper-minibuffer-emacs-face 2504@item viper-minibuffer-emacs-face 'viper-minibuffer-emacs-face
2505These faces control the appearance of the minibuffer text in the 2505These faces control the appearance of the minibuffer text in the
2506corresponding Viper states. You can change the appearance of these faces 2506corresponding Viper states. You can change the appearance of these faces
2507through Emacs' customization widget, which is accessible through the 2507through Emacs's customization widget, which is accessible through the
2508menubar. 2508menubar.
2509 2509
2510Viper is located in this widget under the @emph{Emulations} customization 2510Viper is located in this widget under the @emph{Emulations} customization
@@ -3205,7 +3205,7 @@ in the appropriate major mode hooks.
3205 3205
3206The above discussion concerns only the movement commands. In regular 3206The above discussion concerns only the movement commands. In regular
3207expressions, words remain the same as in Emacs. That is, the expressions 3207expressions, words remain the same as in Emacs. That is, the expressions
3208@code{\w}, @code{\>}, @code{\<}, etc., use Emacs' idea of what is a word, 3208@code{\w}, @code{\>}, @code{\<}, etc., use Emacs's idea of what is a word,
3209and they don't look into the value of variable 3209and they don't look into the value of variable
3210@code{viper-syntax-preference}. This is because Viper avoids changing 3210@code{viper-syntax-preference}. This is because Viper avoids changing
3211syntax tables in order to not thwart the various major modes that set these 3211syntax tables in order to not thwart the various major modes that set these