|Reported by:||Owned by:|
Upcoming update to grep.
We would like to make a new bug-fix-only release of grep soon, so here is a snapshot of the latest sources. Please build and test on whatever systems you can find, and let us know how that goes -- reports of success are welcome, too. grep snapshot: http://meyering.net/grep/grep-ss.tar.xz 1.3 MB http://meyering.net/grep/grep-ss.tar.xz.sig http://meyering.net/grep/grep-2.22.29-83df.tar.xz Here are the NEWS entries: ** Bug fixes Binary files are now less likely to generate diagnostics and more likely to yield text matches. grep now reports "Binary file FOO matches" and suppresses further output instead of outputting a line containing an encoding error; hence grep can now report matching text before a later binary match. Formerly, grep reported FOO to be binary when it found an encoding error in FOO before generating output for FOO, which meant it never reported both matching text and matching binary data; this was less useful for searching text containing encoding errors in non-matching lines. [bug introduced in grep-2.21] grep -c no longer stops counting when finding binary data. [bug introduced in grep-2.21] grep no longer outputs encoding errors in unibyte locales. For example, if the byte '\x81' is not a valid character in a unibyte locale, grep treats the byte as binary data. [bug introduced in grep-2.21] grep -oP is no longer susceptible to an infinite loop when processing invalid UTF8 just before a match. [bug introduced in grep-2.22] --exclude and related options are now matched against trailing parts of command-line arguments, not against the entire arguments. This partly reverts the --exclude-related change in 2.22. [bug introduced in grep-2.22] --line-buffer is no longer ineffective when combined with -l. [bug introduced in grep-2.5] -xw is now equivalent to -x more consistently, with -P and with backrefs. [bug only partially fixed in grep-2.19]
Change History (3)
Note: See TracTickets for help on using tickets.