Andrew Gallant b034b77798 Don't replace NUL bytes when searching binary files as text. ... This was a result of misinterpreting a feature in grep where NUL bytes are replaced with \n. The primary reason for doing this is to avoid excessive memory usage on truly binary data. However, grep only does this when searching binary files as if they were binary, and which only reports whether the file matched or not. When grep is told to search binary data as text (the -a/--text flag), then it doesn't do any replacement so we shouldn't either. In general, this makes sense, because the user is essentially asserting that a particular file that looks like binary is actually text. In that case, we shouldn't try to replace any NUL bytes. ripgrep doesn't actually support searching binary data for whether it matches or not, so we don't actually need the replace_buf function. However, it does seem like a potentially useful feature.		2016-09-25 21:26:49 -04:00
..
hay.rs	Add integration tests.	2016-09-09 22:58:30 -04:00
tests.rs	Don't replace NUL bytes when searching binary files as text.	2016-09-25 21:26:49 -04:00
workdir.rs	Add integration tests.	2016-09-09 22:58:30 -04:00