Re: findstr doesn't always find
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 16:55:10 -0600
"jkwold" <jkwold@xxxxxxxxxx> wrote in message
news:1172521677.106382.103580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
cygwin's grep gave the proper results once I ensured that all 0x0d ==
CR were stripped from the relevant files -- as a bonus said grep
properly handled search strings longer than 115+ chars. Example:
grep -F -f SR_req\'d *def
Jon
On Feb 26, 11:23 am, "jkwold" <jkw...@xxxxxxxxxx> wrote:
I've got cygwin installed, so I'll see how its grep holds up.
This doesn't answer you question directly but Perl is practically
designed for such problems -- in many cases these changes become
litterally one line programs.
ActivePerl (.com) for Win32 is excellent.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- findstr doesn't always find
- From: jkwold
- Re: findstr doesn't always find
- From: jkwold
- findstr doesn't always find
- Prev by Date: Re: findstr doesn't always find
- Next by Date: Re: findstr doesn't always find
- Previous by thread: Re: findstr doesn't always find
- Next by thread: Re: findstr doesn't always find
- Index(es):
Relevant Pages
|
Loading