[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: grep bug?
From: |
Eli Zaretskii |
Subject: |
Re: grep bug? |
Date: |
Thu, 15 Jan 2004 10:35:48 +0200 |
> From: "David Walker" <address@hidden>
> Date: Wed, 14 Jan 2004 21:09:02 -0700
>
> I have a file named test.txt that looks like:
>
> 111Line1
> 222Line2
> 222Line2
> 333Line3
> 222Line2
> 999Line9
>
> Using this:
>
> grep -e 222 test.txt
>
> gives me what I expect:
>
> 222Line2
> 222Line2
> 222Line2
>
> grep -e '222' test.txt gives me nothing. Is the help wrong, or is it
> something I'm doing? I'm using Windows 2000 SP3.
It's a bug in the Windows port of Grep: it's startup code should
remove the quote characters, to emulate what the Unix shell does.
To work around that, use double quotes "..." instead.
- grep bug?, David Walker, 2004/01/14
- Re: grep bug?,
Eli Zaretskii <=