emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Richard Kojedzinszky writes:

Browse Source 
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.
This commit is contained in:
Eric Andersen 2004-02-06 10:36:08 +00:00
parent fa06a77040
commit 5cc90eade5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
editors/vi.c
View File

@ -19,7 +19,7 @@
*/ */
static const char vi_Version[] = 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: * 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 // if we are at the next word's first char
// step back one char // step back one char
// but check the possibilities when it is true // 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])) || (ispunct(dot[-1]) && !ispunct(dot[0]))
|| (isalnum(dot[-1]) && !isalnum(dot[0])))) || (isalnum(dot[-1]) && !isalnum(dot[0]))))
dot--; // move back off of next word dot--; // move back off of next word