Richard Kojedzinszky writes:

Hi All,

I aplogoize for the mistake, but i have just recognized that somehow the
last patch I sent in was wrong, and a '0' was instead of a '-1'. Because
of this, vi does behave the wrong way. So again, it should be the last
patch for vi. This is for pre7.

diff --git a/editors/vi.c b/editors/vi.c
index 57b011444bc4d3b512fafd6c4b81b91731537336..1932742ecd84b9da931697e95bc6460e9f3d2419 100644 (file)
--- a/editors/vi.c
+++ b/editors/vi.c
@@ -19,7 +19,7 @@
  */
 
 static const char vi_Version[] =
-       "$Id: vi.c,v 1.32 2004/02/04 11:19:44 andersen Exp $";
+       "$Id: vi.c,v 1.33 2004/02/06 10:36:08 andersen Exp $";
 
 /*
  * To compile for standalone use:
@@ -1672,7 +1672,7 @@ static Byte find_range(Byte ** start, Byte ** stop, Byte c)
                // if we are at the next word's first char
                // step back one char
                // but check the possibilities when it is true
-               if (dot > text && ((isspace(dot[0]) && !isspace(dot[0]))
+               if (dot > text && ((isspace(dot[-1]) && !isspace(dot[0]))
                                || (ispunct(dot[-1]) && !ispunct(dot[0]))
                                || (isalnum(dot[-1]) && !isalnum(dot[0]))))
                        dot--;          // move back off of next word