GNU logs - #28304, boring messages

Message sent to bug-grep@HIDDEN:

Subject: bug#28304: Feature Request - Quit on Non Match
Resent-From: Adam Danischewski <adam.danischewski@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-grep@HIDDEN
Resent-Date: Thu, 31 Aug 2017 14:44:02 +0000
Resent-Message-ID: <handler.28304.B.150419062118416 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 28304 <at> debbugs.gnu.org
MIME-Version: 1.0
From: Adam Danischewski <adam.danischewski@HIDDEN>
Date: Thu, 31 Aug 2017 10:43:30 -0400
Message-ID: <CAOQZJ0Hb7fsHjDrfGViRyQ742ux4qYPVf5Op74f5LWRVvWB4dA@HIDDEN>
Content-Type: multipart/alternative; boundary="001a113d638c0287e705580dabed"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--001a113d638c0287e705580dabed
Content-Type: text/plain; charset="UTF-8"

I've been writing parsers and it would be really nice if grep could do the
following:

*grep --quit-nm 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*

If you:
*grep -m 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*

Only the first match of the header block gets printed, yet it would be nice
if grep in O(n), could simply be on the look out for the first failure to
match the -o context and quit at --quit-nm non-match occurrences.

--001a113d638c0287e705580dabed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>I&#39;ve been writing parsers and it would =
be really nice if grep could do the following: <br></div><div>=C2=A0<br></d=
iv><b>grep --quit-nm 1 -Pno &quot;^[ \t\f]*#.*$&quot; &lt;(sed -n &#39;2,$p=
&#39; gen_ent.bsh)</b><br><br></div>If you: <br><b>grep -m 1 -Pno &quot;^[ =
\t\f]*#.*$&quot; &lt;(sed -n &#39;2,$p&#39; gen_ent.bsh)</b><br><br></div>O=
nly the first match of the header block gets printed, yet it would be nice =
if grep in O(n), could simply be on the look out for the first failure to m=
atch the -o context and quit at --quit-nm non-match occurrences. <br><br></=
div>

--001a113d638c0287e705580dabed--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Adam Danischewski <adam.danischewski@HIDDEN>
Subject: bug#28304: Acknowledgement (Feature Request - Quit on Non Match)
Message-ID: <handler.28304.B.150419062118416.ack <at> debbugs.gnu.org>
References: <CAOQZJ0Hb7fsHjDrfGViRyQ742ux4qYPVf5Op74f5LWRVvWB4dA@HIDDEN>
X-Gnu-PR-Message: ack 28304
X-Gnu-PR-Package: grep
Reply-To: 28304 <at> debbugs.gnu.org
Date: Thu, 31 Aug 2017 14:44:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-grep@HIDDEN

If you wish to submit further information on this problem, please
send it to 28304 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
28304: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D28304
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-grep@HIDDEN:

Subject: bug#28304: Feature Request - Quit on Non Match
Resent-From: arnold@HIDDEN
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-grep@HIDDEN
Resent-Date: Thu, 31 Aug 2017 14:54:02 +0000
Resent-Message-ID: <handler.28304.B28304.150419121319325 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: adam.danischewski@HIDDEN, 28304 <at> debbugs.gnu.org
From: arnold@HIDDEN
Message-Id: <201708311453.v7VErUtT024120@HIDDEN>
Date: Thu, 31 Aug 2017 08:53:30 -0600
References: <CAOQZJ0Hb7fsHjDrfGViRyQ742ux4qYPVf5Op74f5LWRVvWB4dA@HIDDEN>
In-Reply-To: <CAOQZJ0Hb7fsHjDrfGViRyQ742ux4qYPVf5Op74f5LWRVvWB4dA@HIDDEN>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Adam Danischewski <adam.danischewski@HIDDEN> wrote:

> I've been writing parsers and it would be really nice if grep could do the
> following:
>
> *grep --quit-nm 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*
>
> If you:
> *grep -m 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*
>
> Only the first match of the header block gets printed, yet it would be nice
> if grep in O(n), could simply be on the look out for the first failure to
> match the -o context and quit at --quit-nm non-match occurrences.

I may be misunderstanding what you want, but something like

	awk '/pattern to match/ { print ; continue }
		{ exit 0}' file

might do what I think you want - exit on first non match.

If gawk can do the same matching you're doing with grep -Pno, that
is a different question.

HTH,

Arnold

Message sent to bug-grep@HIDDEN:

Subject: bug#28304: Feature Request - Quit on Non Match
Resent-From: Adam Danischewski <adam.danischewski@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-grep@HIDDEN
Resent-Date: Thu, 31 Aug 2017 17:51:02 +0000
Resent-Message-ID: <handler.28304.B28304.150420185724418 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: arnold@HIDDEN
Cc: 28304 <at> debbugs.gnu.org
MIME-Version: 1.0
In-Reply-To: <201708311453.v7VErUtT024120@HIDDEN>
References: <CAOQZJ0Hb7fsHjDrfGViRyQ742ux4qYPVf5Op74f5LWRVvWB4dA@HIDDEN>
 <201708311453.v7VErUtT024120@HIDDEN>
From: Adam Danischewski <adam.danischewski@HIDDEN>
Date: Thu, 31 Aug 2017 13:50:49 -0400
Message-ID: <CAOQZJ0GMpE9o8aszYH6R31AYAcAd9Hn3UB2mVidDQ=uNcbHs5Q@HIDDEN>
Content-Type: multipart/alternative; boundary="001a11482d10f5d9be05581048cd"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--001a11482d10f5d9be05581048cd
Content-Type: text/plain; charset="UTF-8"

Yes, awk can handle it except for maybe very large files. I was trying to
keep it restricted to grep, grep is already counting matches with -m but
maybe GNU views this direction as becoming too programmatic from what the
original vision of grep is?

awk '{if($0~/^[ \t\f#]+/)print $0;else exit}' gen_ent.bsh

Thanks anyway,
 +AMD

On Thu, Aug 31, 2017 at 10:53 AM, <arnold@HIDDEN> wrote:

> Adam Danischewski <adam.danischewski@HIDDEN> wrote:
>
> > I've been writing parsers and it would be really nice if grep could do
> the
> > following:
> >
> > *grep --quit-nm 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*
> >
> > If you:
> > *grep -m 1 -Pno "^[ \t\f]*#.*$" <(sed -n '2,$p' gen_ent.bsh)*
> >
> > Only the first match of the header block gets printed, yet it would be
> nice
> > if grep in O(n), could simply be on the look out for the first failure to
> > match the -o context and quit at --quit-nm non-match occurrences.
>
> I may be misunderstanding what you want, but something like
>
>         awk '/pattern to match/ { print ; continue }
>                 { exit 0}' file
>
> might do what I think you want - exit on first non match.
>
> If gawk can do the same matching you're doing with grep -Pno, that
> is a different question.
>
> HTH,
>
> Arnold
>

--001a11482d10f5d9be05581048cd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Yes, awk can handle it except for maybe very lar=
ge files. I was trying to keep it restricted to grep, grep is already count=
ing matches with -m but maybe GNU views this direction as becoming too prog=
rammatic from what the original vision of grep is? <br><br>awk &#39;{if($0~=
/^[ \t\f#]+/)print $0;else exit}&#39; gen_ent.bsh<br><br></div>Thanks anywa=
y, <br></div>=C2=A0+AMD <br></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Aug 31, 2017 at 10:53 AM,  <span dir=3D"ltr">&lt;<=
a href=3D"mailto:arnold@HIDDEN" target=3D"_blank">arnold@HIDDEN</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adam Danischewski &lt;=
<a href=3D"mailto:adam.danischewski@HIDDEN">adam.danischewski@HIDDEN<=
/a>&gt; wrote:<br>
<br>
&gt; I&#39;ve been writing parsers and it would be really nice if grep coul=
d do the<br>
&gt; following:<br>
&gt;<br>
&gt; *grep --quit-nm 1 -Pno &quot;^[ \t\f]*#.*$&quot; &lt;(sed -n &#39;2,$p=
&#39; gen_ent.bsh)*<br>
&gt;<br>
&gt; If you:<br>
&gt; *grep -m 1 -Pno &quot;^[ \t\f]*#.*$&quot; &lt;(sed -n &#39;2,$p&#39; g=
en_ent.bsh)*<br>
&gt;<br>
&gt; Only the first match of the header block gets printed, yet it would be=
 nice<br>
&gt; if grep in O(n), could simply be on the look out for the first failure=
 to<br>
&gt; match the -o context and quit at --quit-nm non-match occurrences.<br>
<br>
I may be misunderstanding what you want, but something like<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 awk &#39;/pattern to match/ { print ; continue =
}<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 { exit 0}&#39; file=
<br>
<br>
might do what I think you want - exit on first non match.<br>
<br>
If gawk can do the same matching you&#39;re doing with grep -Pno, that<br>
is a different question.<br>
<br>
HTH,<br>
<br>
Arnold<br>
</blockquote></div><br></div>

--001a11482d10f5d9be05581048cd--

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.