Date: Wed, 28 Jul 2010 17:48:29 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Gabor Kovesdan <gabor@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, "b. f." <bf1783@googlemail.com> Subject: Re: BSD grep fixes Message-ID: <86wrsfk3oy.fsf@ds4.des.no> In-Reply-To: <4C504DEA.9070405@FreeBSD.org> (Gabor Kovesdan's message of "Wed, 28 Jul 2010 17:34:02 %2B0200") References: <AANLkTimJiV1s3KNsCKsqT_dNiqMyRuOFpK47AD4QyMUO@mail.gmail.com> <4C5040E8.3050304@FreeBSD.org> <AANLkTi=d0Ev_JwE5AFHNMSyPrWYTd7PYTSGn2W91prHA@mail.gmail.com> <4C504DEA.9070405@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gabor Kovesdan <gabor@FreeBSD.org> writes: > b. f. <bf1783@gmail.com> writes: > > I don't think that the current behavior of bsdgrep is necessarily bad > > -- in fact it seems to me to be simple and intuitive: nothing is > > excluded or included implicitly, and (I think) the last match wins, > > unlike in gnu grep. > Ok, thanks, then I'll just document it. Uh, no. GNU grep's behavior is consistent with just about everything else that has --include / --exclude options, e.g. tar and rsync. Please change BSD grep's behavior to match GNU grep's. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wrsfk3oy.fsf>