bug#18892: few test failure with 'grep-2.20.72-d512'

Hello, On 10/29/2014 02:29 PM, Jim Meyering wrote: Thanks to many fixes and improvements by Paul Eggert and Norihiro Tanaka, here is a pre-release snapshot: grep snapshot: http://meyering.net/grep/grep-ss.tar.xz 1.2 MB http://meyering.net/grep/grep-ss.tar.xz.sig

bug#18892: few test failure with 'grep-2.20.72-d512'

Hello, On 11/01/2014 07:06 PM, Jim Meyering wrote: On NetBSD 6.1.4, these fail: XFAIL: equiv-classes FAIL: symlink FAIL: word-multibyte ... However, I'll need more information to understand the symlink failure. Normally the log file contains verbose output information (resulting

bug#18892: few test failure with 'grep-2.20.72-d512'

Hello, On 11/01/2014 10:39 PM, Paul Eggert wrote: Assaf Gordon wrote: $ ../../../src/grep -r '^' ; echo $? a:a b:b ../../../src/grep: c: Inappropriate file type or format ../../../src/grep: d: Inappropriate file type or format ../../../src/grep: e: Inappropriate file type or format 2 What

bug#19005: [platform-testers] new snapshot available: grep-2.20.83-06900

On 11/09/2014 05:30 PM, Assaf Gordon wrote: On 11/09/2014 04:00 PM, Jim Meyering wrote: Testing the first snapshot exposed several problems, and most have been addressed. The sole remaining problem is the failure of an expensive (not run by default: big-match) that makes most systems run out

bug#19071: new snapshot available: grep-2.20.90-a07a4

Hello, On 11/16/2014 12:07 PM, Jim Meyering wrote: Here is a third pre-release snapshot. http://meyering.net/grep/grep-2.20.90-a07a4.tar.xz ... No failures on: debian 7.6 gnewsense 3.1 (=debian 6) ubuntu14.04.01 trisquel 6.0.1 (=ubuntu 12 LTS) centos 6.5 centos 7 openSuSE 13.1

bug#22443: new snapshot available: grep-2.22.33-43f6

On 02/03/2016 01:07 AM, Jim Meyering wrote: http://meyering.net/grep/grep-2.22.33-43f6.tar.xz No failures on: Mac OS X v10.11.3, v10.10.5, v10.9.5 Ubuntu 14, aarch64 Fedora 20, ppc64 Fedora 21, ppc64le OpenSolaris 5.10/5.11 on i86pc, suv4u/sub4v

bug#22443: Subject: new snapshot available: grep-2.22.31-8b6a

hello, > On Jan 28, 2016, at 19:36, Jim Meyering wrote: > > http://meyering.net/grep/grep-2.22.31-8b6a.tar.xz Testing from the above tarball, no test failures on the following systems: Fedora-21,ppc64le Fedora-20,ppc64 Ubuntu-14,aarch64 AIX 7.1,power7

bug#22443: new snapshot available: grep-2.22.30-e07b

Hello, > On Jan 23, 2016, at 23:42, Jim Meyering wrote: > > grep snapshot: > http://meyering.net/grep/grep-2.22.30-e07b.tar.xz One regression for 2.22.30 vs 2.22.29 on OpenSolaris 5.10, both x86pc and sun4v, possibly related to this machine having an older shell: $

bug#23031: reporting write errors and handling SIGPIPE

Hello, First, Attached is a patch that adds errno information to 'write error' messages, e.g.: $ grep [...] > /dev/full grep: write error: No space left on device I hope it is self-explanatory enough (comments and suggestions are welcomed). Second, On one gnu/linux server I'm

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

bug#23031: reporting write errors and handling SIGPIPE

Hello, On 03/17/2016 02:49 PM, Paul Eggert wrote: On 03/16/2016 09:14 AM, Assaf Gordon wrote: Attached is a patch that adds errno information to 'write error' messages Thanks, I installed the attached somewhat-tweaked version of that. Among other things I renamed the new static functions

bug#22899: new snapshot available: grep-2.23.7-9e28

Hello, On 03/03/2016 08:57 PM, Jim Meyering wrote: grep snapshot: http://meyering.net/grep/grep-2.23.7-9e28.tar.xz No failures (with minimal build, no pcre) on: CentOS 7 + 6.5, amd64 Ubuntu 14.04, amd64 Ubuntu 15.04 amd64 + i686 openSUSE 42.1, 13.1, amd64 Fedora 23, 22,

bug#24505: getprogname vs. AIX [was: new snapshot available: grep-2.25.92-f3e9

Hello Jim, On 09/22/2016 12:25 AM, Jim Meyering wrote: Gordon reported this off-list: On AIX-7.1 32bit, compilation fails due to gnulib's new 'getprogname' module: CC getprogname.o getprogname.c: In function 'getprogname': getprogname.c:45:4: error: #error "getprogname module not

bug#24602: grep-2.26 make check fails on i686

Hello, > On Oct 3, 2016, at 17:48, Jaroslav Skarvada wrote: > > Reproduced on Fedora Rawhide, gcc-6.2.1: > > [...] > Full build log: > https://kojipkgs.fedoraproject.org/work/tasks/8044/15928044/build.log > x86_64 seems to work OK As a side note, these are gnulib tests

bug#26576: -v when used with -C

On Thu, Apr 20, 2017 at 02:34:47PM -0500, Eric Blake wrote: On 04/20/2017 11:51 AM, Assaf Gordon wrote: If I may suggest the following sed program: $ sed -n ':x 1,2{N;bx} ; /UGLY/{ N;N;z;bx }; /./P;N;D' file Works as long as lines 1 and 2 do not contain UGLY. But misbehaves if UGLY appears

bug#26576: -v when used with -C

Hello, On Thu, Apr 20, 2017 at 11:26:47AM -0500, Eric Blake wrote: On 04/20/2017 10:37 AM, 積丹尼 Dan Jacobson wrote: I want to do $ cat file|some_program but I must must exclude the UGLY line and its two neighbors. OK I have found the UGLY line, and its two neighbors $ grep -C 2 UGLY file bla

bug#28081: way to change line number separator from colon to space?

Hello, On 13/08/17 12:45 PM, Marcel Partap wrote: >> One way: >> grep | sed "s/:/ /" > Thanks, obvious approach, but loses colour  Few things: First, you can force grep to output color with: grep --color=always | sed 's/:/ /' Second, If you grep on a shell-glob (e.g. "*.txt"), you

bug#27532: getprogname: support for qemu

Hello Bruno and all, > On Jun 29, 2017, at 12:26, Bruno Haible wrote: > > When running the testsuite of grep-3.0 with qemu user mode, some tests fail. > [...] > *** 1 > ! grep: g:4: Unmatched [... > --- 1 > ! /tmp/grep-3.0/build-arm64/src/grep: g:4: Unmatched [... >

bug#30525: Unexpected matches for input data from a patch file

Hello Markus, I believe there are actually several different issues here, perhaps it's worth stating them explicitly to ensure we're on the same page. On 2018-03-01 12:52 AM, SF Markus Elfring wrote: * Does the tool “grep” output any extra colour information also for    matched tab

bug#32704: Can grep search for a line feed and a null character at the same time?

Hello, On 15/09/18 11:57 AM, 21na...@gmail.com wrote: Le 15/09/2018 à 19:06, Eric Blake a écrit : On 9/15/18 11:43 AM, 21na...@gmail.com wrote: But is it at least possible to find “\x0A\x00” with grep? If you bend the rules by throwing -P into the mix, yes :) So it is possible to find

bug#36764: grep -q throwing up No such file or directory error

tag 36764 notabug close 36764 stop Hello, (answering out-of-order) On Mon, Jul 22, 2019 at 06:12:10PM +0100, Lewis Farnworth wrote: > To reiterate: > > if grep -q "thing_i'm_looking_for" $variable_i'm_looking_in; then > > doesn't work, on CentOS 7 or Debian 9. This is incorrect usage, and

bug#41687: regex search for indexed files

tag 41687 notabug close 41687 stop Hello, On 2020-06-03 8:27 a.m., Peng Yu wrote: grep can do regex search but it needs to scan each file. When the number of files are large, it can be slow. Is there an alternative tool that can do regex search in the indexed files (including .docx .pdf and