Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5EB95.1242248A" Subject: FW: 1.5.18: grep -f option broken Date: Thu, 17 Nov 2005 08:36:32 -0800 Message-ID: From: "Chris Milam" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Note-from-DJ: This may be spam ------_=_NextPart_001_01C5EB95.1242248A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In the latest release of grep (2.5.1a-2), I believe that the -f option (read expressions from a file) is no longer working. This option is documented as follows: -f FILE, --file=3DFILE Obtain patterns from FILE, one per line. The empty file con- tains zero patterns, and therefore matches nothing. However, it appears that no match of any input is ever found for any set of strings in the file specified by -f. This functionality was working in an earlier release (I regret to say that I cannot remember the last time it was working but it was a release within the last year, I think). I have included two example scripts that illustrate the problem: -----grepgood----- ( echo $BASH; cat <