Re: What does Emacs on w32 know that grep can't figure out?

[PJ Weisberg]

On Fri, Oct 1, 2010 at 12:09 AM, Eli Zaretskii <address@hidden> wrote:
> Grep treats its input as a stream of bytes.  So it will not be able to
> support any encoding where each character, including ASCII, takes 2 or
> more bytes.  Unless you also encode the search string in the same
> encoding, that is.

In 5 minutes of testing I see that grep (GNU grep 2.6.3) doesn't
handle null bytes in the pattern.  (String ends at the first null, as
c-strings are wont to do.)

On Fri, Oct 1, 2010 at 5:02 AM, Eli Zaretskii <address@hidden> wrote:
>> From: Lennart Borgman <address@hidden>
>> Date: Fri, 1 Oct 2010 11:28:49 +0200
>> Cc: address@hidden, address@hidden
>>
>> > What's wrong with "M-x occur" and/or "M-x multi-occur"?
>>
>> They does not do what grep does.
>
> Like what?

Recursively act on all files in a directory, for one.

>> And as I said opening the files in a buffer will be bad because of 
>> performance.
>
> What do you think Grep does?  Doesn't it open the files and read them?

One line at a time.  That'll make a difference for large files.