From owner-freebsd-bugs@freebsd.org Wed Apr 19 23:19:06 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D83B5D460F8 for ; Wed, 19 Apr 2017 23:19:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C818EFB1 for ; Wed, 19 Apr 2017 23:19:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3JNJ6bf058930 for ; Wed, 19 Apr 2017 23:19:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 105221] grep(1): `grep -w -F ""` issue Date: Wed, 19 Apr 2017 23:19:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: gnu X-Bugzilla-Version: 6.2-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bsdports@kyle-evans.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 23:19:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D105221 Kyle Evans changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bsdports@kyle-evans.net, | |emaste@freebsd.org --- Comment #3 from Kyle Evans --- Some notes: bsdgrep(1) is also affected in a different way by this old, old bug, so some notes: gnugrep currently in base still exhibits the original behavior bsdgrep will match the string textproc/gnugrep will fail to match, presumably because it matches the 0-le= ngth BOL at the beginning of the string and the character immediately following = it ("q") is a word character Here's some other interesting behavior from textproc/gnugrep: $ echo "" | fgrep -w "" # Empty string, exit =3D 0, OK, that's..interesting $ echo "qaz" | fgrep -w "" # exit =3D 1, expected $ echo " qaz" | fgrep -w "" qaz $ printf "" | fgrep -w "" # exit =3D 1, expected On one hand, I don't agree with the idea that a 0-length match can *ever* produce a whole-word match- this seems misleading and probably not a practi= cal use case. On the other hand, this is technically correct behavior because the 0-length match is at the beginning of the string with a non-word-character on its ot= her side. --=20 You are receiving this mail because: You are the assignee for the bug.=