#432 Grepwin in not able to process some when I run against the containing directory, but it is able to process the file when I ran against the file

[Swin]

II have a preset RegEx pattern that should match and replace characters in files. However, if I run grepwin against the containing directory, some files are not processed (no matches found). If I run against the specific file that apparently contained no matches, grepwin works as expected, matches are found and replaced.

The really odd thing here is that I have been using this for the past several weeks and it has been working flawlessly, ever after the recent update to v1.6.12

I can see if I can provide some test files if required.

[Swin]

It would appear as though the files that grepwin is struggleing with, it belives they are BINARY files. Not quite sure why this is the case. All other files are seen as ANSI, but they should all be similar. The only real differnt is the the files grepwin thinks are binary, are the las to of the tail log, whereas the others are a full circular log file.

[Stefan Kueng]

Can you attach the files or just one file that shows this behavior to this issue?

[Swin]

Hi Stefan. It looks as though there si some corruption in the log file. Thtas why grepwin sees it as a binary,I suppose I will just have to set the "include binary file option"

The screeshot image show what in mean.

I think we can close this ticket.

[Stefan Kueng]

Yes. the NUL bytes in the file are the reason grepWin treats those files as binary.