From owner-freebsd-bugs Tue Apr 14 21:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11196 for freebsd-bugs-outgoing; Tue, 14 Apr 1998 21:10:06 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11138; Tue, 14 Apr 1998 21:10:01 -0700 (PDT) (envelope-from gnats) Date: Tue, 14 Apr 1998 21:10:01 -0700 (PDT) Message-Id: <199804150410.VAA11138@hub.freebsd.org> To: freebsd-bugs Cc: From: Bill Fenner Subject: Re: bin/6301: vi bug Reply-To: Bill Fenner Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/6301; it has been noted by GNATS. From: Bill Fenner To: John-Mark Gurney Cc: freebsd-gnats-submit@hub.freebsd.org Subject: Re: bin/6301: vi bug Date: Tue, 14 Apr 1998 21:03:48 PDT John-Mark Gurney wrote: > > #define MASK(len) ((0xffffffff>>(32-(len)))<<(32-(len))) > ab c d dcb e f fea > > > If i position the cursor on the first ``<'' on the above > > do you mean `('? because vi doesn't do matching of angle braces... Yes it does; that's his problem. Greg wants the behavior that's described in the documentation: The cursor moves to the parenthesis or curly brace which .i matches the parenthesis or curly brace found at the current cursor position or which is the closest one to the right of the cursor on the line. Note the last phrase - when Greg has his cursor on the first <, he wants it to match on the first paren you labelled "e", since that is the closest one to the right of the cursor on the line. Instead, since vi learned how to match <>'s, it beeps since there's no match. Since matching <>'s is useful when writing HTML but not when programming, Greg suggested (in a later message) a "set" option to enable <> matching; I think I agree. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message