bug#23269: new snapshot available: grep-2.24.13-bed6

On 04/11/2016 09:13 AM, Jim Meyering wrote: This problem is likely to affect many more programs than just grep, so we presume it will be fixed promptly I am not sure about how promptly it'll be fixed in glibc, as this may require more developer oomph in the localedata area. Although Bruno

bug#23269: new snapshot available: grep-2.24.13-bed6

I plan to release grep-2.25 this week, so here's a snapshot of the latest. Please beat it up and report success and failure here. Thanks to Paul Eggert for fixing so many bugs (and especially for the mbrtowc workaround in gnulib), and to Assaf Gordon for the initial patch to make many of grep's

bug#23234: unexpected results with charset handling in GNU grep 2.23

On Sun, Apr 10, 2016 at 10:19 PM, Paul Eggert wrote: > Jim Meyering wrote: >> >> With this fix, I would like to make yet another grep release. >> Does anyone have any pending changes we should consider? > > > I did a bit of bug triage, closing some bug reports and fixing one

bug#23267: suggestion: silently ignore EPIPE errors when SIGPIPE is set to 'ignore'

Assaf Gordon wrote: With the above change, if SIGPIPE is set to 'ignore' (e.g. by the shell or python), then grep would exit with "write error: Broken Pipe". Based on recent suggestion from Pádraig Brady I don't see why this is would be a good idea. grep should report write errors. A caller

bug#23267: suggestion: silently ignore EPIPE errors when SIGPIPE is set to 'ignore'

Hello, This is a small addition to a recent change: 1cec27a7f0e5c7bdc44a88ef51af09f87a8cbc24 grep: use errno consistently in write diagnostics With the above change, if SIGPIPE is set to 'ignore' (e.g. by the shell or python), then grep would exit with "write error: Broken Pipe". Based