bug#33552: Possible bug with handling -I option

Jason, thanks for reporting this grep bug . It strikes me that this is related to another grep bug concerning the "Binary files ..." message. Although they're not the same bug, it's likely that fixing one will also entail fixing the other. So

bug#33972: grep -vf <() filters all rows

> I have to pre-check for an empty set before passing it to grep: > ... > Workaround: You're right that the empty pattern matches every line, since every line has an empty string in it somewhere. This is considered to be a feature of grep, not a bug. As you have a workaround I'm closing the bug re

bug#34078: typo in gnu grep's manual ?

Thanks for reporting that typo in the grep manual. I installed the attached patch to fix it. From 9500f11eaa5ec3ae2e31c51b796102ace570af1c Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 2 Jan 2020 01:10:10 -0800 Subject: [PATCH] =?UTF-8?q?doc:=20fix=20missing=20=E2=80=9Cmore=E2=80=9D?= =?U

bug#35051: Fwd: grep

Re : Unfortunately the stackoverflow URLs you sent no longer work. If you have a specific, self-contained bug report about grep, please follow up here.

bug#35681: grep's ./configure doesn't work with plain /bin/sh

As this was a bug (now fixed) in Bash not grep, I'm closing the grep bug report.

bug#36148: inconsistent behaviour with anchored regex containing back-references

Yes, back-references don't work very well. This looks to be the same bug as Bug#26864 so I have merged the two bug reports.

bug#36815: dfa up to date?

On 7/28/19 4:03 PM, Paul Eggert wrote: > Before the next grep release, surely. But I don't have an ETA for that either. This is down now so I'm closing the bug report.

bug#36960: mistake with v param

On 8/7/19 8:45 AM, Daniele Grassini wrote: > so why the '-o' option check the regular exp, but the '-v' don't do his job?? The -v option was working as documented. It means, "select lines that *don't" match the pattern", and since all input lines matched your pattern grep didn't output anything.

bug#37212: Incorrect --exclude description with 'grep --help'

Thanks for the bug report. I installed the attached (slightly different) patch to fix the bug and inconsistency. >From 61bbb574dcf350830b526bea61250e30d95057d0 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 2 Jan 2020 01:54:47 -0800 Subject: [PATCH] doc: fix --exclude description in man pag

bug#37607: How to use Grep with Using -o

On 10/3/19 8:54 AM, Matt Zand wrote: > Is it possible to output symbols which constitute non-matched parts of > text? For instance, I expect > > printf "banana\napple" | grep --invert-match --only-matching 'ban' > > to produce > > ana > apple > > or > > apple > > , but it doesn't produce any

bug#38322: GCC optimize levels makes huge impact on performance

On 11/22/19 5:52 PM, Paul Eggert wrote: > If we do want to tune grep for set-like operations, that suggests doing some > surgery to its internals rather than merely fiddling with -O flags. Since I last wrote, some of that surgery has been done by another grep contributor, and a simple 'grep -f fil

bug#32943: grep pattern < fifo fails on Cygwin (and MinGW), but not on Linux

On 2020-01-02 02:09, Paul Eggert wrote: On 10/8/18 11:10 AM, Houder wrote: We have to wait until Corinna Vinschen returns from holidays (end of october), because Corinna Vinschen is the only one who can deal with the executive. Corinna later pushed a patch for this Cygwin bug

bug#32073: Improvements in Grep (Bug#32073)

Hi Arnold, Annoying in the sense that you have to specify it with every usage. In a company where you have 10+ developers grepping over various logs, each one has to remember to add the extra parameter. Easier would be to have some kind of global configuration that the system admin can set and deve

bug#32073: Improvements in Grep (Bug#32073)

OK, thanks for the input. Arnold Sergiu Hlihor wrote: > Hi Arnold, > Annoying in the sense that you have to specify it with every usage. In a > company where you have 10+ developers grepping over various logs, each one > has to remember to add the extra parameter. Easier would be to have some >

bug#38322:

Thank you Paul, I wish you a happy new year! Best regards

bug#29446: GNU grep 3.1 fails test suite when PCRE lacks JIT

Hi Paul, On 2019-12-31 21:41, Paul Eggert wrote: > Re this old bug report : > > I attempted to reproduce this bug on Ubuntu 18.04.3 LTS x86-64, by building > pcre > 8.43 by hand with "./configure --disable-jit --prefix=/tmp/prefix" and then > compiling and building GN

bug#29446: GNU grep 3.1 fails test suite when PCRE lacks JIT

On 1/2/20 10:02 AM, Thomas Deutschmann wrote: Is it suitable for you to run Gentoo in a chrooted environment? Thanks, but I wouldn't consider that easy enough access. I wouldn't have decent debugging tools without further downloading and installing them into the chrooted environment, and I do

bug#29446: GNU grep 3.1 fails test suite when PCRE lacks JIT

Hi, OK, I managed to reproduce the error using pure Debian: $ mkdir /tmp/pcre-test $ cd /tmp/pcre-test $ wget https://ftp.pcre.org/pub/pcre/pcre-8.43.tar.gz $ tar -xaf pcre-8.43.tar.gz $ cd pcre-8.43/ $ ./configure --prefix=/tmp/pcre-test/build \ --with-match-limit-recursion=8192 \ --enable-pcr