On 2024-03-24, Paul Eggert wrote:
> On 2024-03-24 06:06, David G. Pickett wrote:
> > Perhaps the man page should warn users that such last lines are ignored.
>
> They aren't ignored. And the documentation already covers this issue,
> on its very first page:
>
> https://www.gnu.org/software/grep/
On 2023-10-10, Joerg M. Sigle wrote:
> Hello GNU grep team
>
> I have grep (GNU grep) 3.6 on a Debian / Devuan Linux system.
>
> Recently I noticed that when using the -o switch, grep also shows
> the filename for each hit in front of the desired output, and
> a ":" as separator.
> IIRC this was
On 2022-11-27, Klaus Dittrich wrote:
> Given file.txt with three lines:
>
> /usr/local/lib/gdk-pixbuf-2.0
> empty
> /usr/local/lib/libgd2
>
> When I do:
>
> grep gdk file.txt
> this results in : /usr/local/lib/gdk-pixbuf-2.0
>
> Which looks ok for me.
>
> When I do:
>
> grep gdk* file.txt
>
On 2022-09-07, Simon Josefsson via Bug reports for GNU grep wrote:
> Personally, I'd rather have tools exit with an error code on invalid
> uses rather than issuing warning messages.
The warning messages are merely annoying. Returning a non-zero exit
status would break scripts, and in many cases
On 2022-09-07, Simon Josefsson via Bug reports for GNU grep wrote:
> On the other hand, it seems your main problem here is the warning: and I
> agree that is annoying and should be fixed. There doesn't seem to be
> any way to disable it now? It would be nice to fix that.
>
> I think the simples
On 2022-07-08, GUI via Bug reports for GNU grep wrote:
> I'm a beginner for Linux.
> Today, when I was learning the grep command, I used the man
> command to check its manual and found a suspicious point.In its
> DESCRIPTION,it says "grep searches for PATTERN in each FILE.
> A FILE of “-” st
On 2022-05-28, goncholden wrote:
> I was trying to change the colours used for matching temporarily.
> But GREP_COLORS is global in nature.
An environment variable such as GREP_COLORS set by itself on the
command line persists in the environment after it has been set. An
environment variable set
On 2022-05-26, Paul Eggert wrote:
> On 5/25/22 13:48, goncholden via Bug reports for GNU grep wrote:
> >Have been using grep to colour the filename printed by tail using
> >grep, by setting GREP_COLOR. However the setting does not work
> >with GREP_COLORS.
> >
> >Additionally, I could not set colo
On 2019-07-11, Steven Penny wrote:
> Grep does not have a way to disable "-i", "-n" or "-r" options. Those options
> could look like this:
>
>-N, --no-line-number
>-O, --no-ignore-case
>-S, --no-recursive
>
> The single letter choices are not ideal, but "-I" and "-R" were already take
On 2022-02-26, Marja Koivunen wrote:
> I had a directory with filenames that started with “-“
>
> doing grep on that directory for a “string" did not find anything
> although “string was on some of the files”
>
> grep just kept repeating something … FreeBSD
>
> Finally, (with some help) I unders
On 2021-08-10, Paul Eggert wrote:
> On 8/10/21 4:21 PM, Gary Johnson wrote:
> >$ src/grep --file=in in >out
> >$ echo $?
> >1
> >$ od -t o1 in
> >000 360 220 220 205 012
> >005
> >$ cmp in out
> >cmp: EOF on out which is empty
>
On 2021-08-10, Paul Eggert wrote:
> Here is a shell transcript on my platform. Can you compare it to what
> happens on your platform? I am guessing that the first 'echo $?'
> outputs something different but would like to know what it is. Plus
> any other differences.
>
> $ export LC_ALL=en_US.UTF-
On 2021-08-10, Paul Eggert wrote:
> On 8/10/21 8:54 AM, Gary Johnson wrote:
> >The log is pretty big. Would you like it posted here?
>
> It'd be helpful to see tests/surrogate-pair.log. If it's long perhaps
> you could compress it and attach the compressed version to
I built grep-3.6.27-20b4 on a machine running up-to-date Cygwin
3.2.0 and Windows 10 Enterprise Version 10.0.18363 Build 18363.
Running "make check" resulted in the following summary.
Testsuite summary for GNU gre
On 2020-05-14, loic.tregouet wrote:
> Hi,
>
> I've reproduced a strange behaviour of grep command when a file
> name of a single letter is present in current directory .
>
> $ echo a | grep [a-z]
> a
> $ touch t
> $ echo a | grep [a-z]
> $ rm t
> $ echo a | grep [a-z]
> a
> $
>
>
> Any idea ?
On 2020-02-12, Fernando Roa wrote:
> this does not work
> grep yvertohor --include={*.R,*.Rmd}
Did you mean to follow that with an asterisk:
grep yvertohor --include={*.R,*.Rmd} *
Otherwise, grep is waiting for text to appear on stdin. Without -r,
you have to give grep a list of file(s) to
On 2019-05-28, Victor Puertas Carreto wrote:
> Dear gnu team,
>
> I do not receive any output when executing the following grep
> command:
> $ grep -H get_excel_report.py
>
> I checked the usage of the command (see field attached
> grepHelp.jpg). No information is displayed after the execution.
There was some recent discussion on the vim_dev list of a failure to
update a Vim package which was found to be due to an update of grep
from 2.25 to 2.26. The details of the grep behavior are discussed
here:
https://www.linuxquestions.org/questions/slackware-14/pkgtools-grep-bug-in-slackware[64]
On 2016-02-13, Peng Yu wrote:
> Hi,
>
> I know that I can use this to grep two patterns. But it can not
> highlight both patterns.
>
> grep word1 FILE | grep word2
This seems to work:
grep --color=always word1 FILE | grep word2
Regards,
Gary
On 2015-10-21, Jim Meyering wrote:
> On Wed, Oct 21, 2015 at 1:09 PM, Gary Johnson wrote:
> > On 2015-10-18, Jim Meyering wrote:
> >> > I built the snapshot on two systems, a fairly old one running Ubuntu
> >> > 10.04.4 and a newer one running an up-to-date Li
On 2015-10-22, Norihiro Tanaka wrote:
> On Wed, 21 Oct 2015 13:09:14 -0700
> Gary Johnson wrote:
>
> > I also built the snapshot successfully on a Fedora 17 system that I
> > use for real work. I just ran a performance test, FWIW. I searched
> > recursively in o
On 2015-10-18, Jim Meyering wrote:
> > I built the snapshot on two systems, a fairly old one running Ubuntu
> > 10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
> > 'make check' reported the same two failures on both:
> >
> >XFAIL: backref-alt
> >XFAIL: triple-backref
>
> Tha
On 2015-10-17, Jim Meyering wrote:
> I want to release grep-2.22 in just a couple of days.
> This release is motivated largely by the discovery that there has
> been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
> print some lines that did not match. However, there have also been
23 matches
Mail list logo
