From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44941@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
rms@gnu.org
Subject: bug#44941: 28.0.50; M-x grep, perhaps all asynch subprocesses
Date: Mon, 30 Nov 2020 19:46:28 +0300 [thread overview]
Message-ID: <X8Uh5APCdfVsjW0u@protected.rcdrun.com> (raw)
In-Reply-To: <83im9mkdg4.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2020-11-30 19:39]:
> > From: Andreas Schwab <schwab@linux-m68k.org>
> > Cc: rms@gnu.org, 44941@debbugs.gnu.org
> > Date: Mon, 30 Nov 2020 16:47:28 +0100
> >
> > On Nov 30 2020, Eli Zaretskii wrote:
> >
> > >> From: Richard Stallman <rms@gnu.org>
> > >> Cc: 44941@debbugs.gnu.org
> > >> Date: Sun, 29 Nov 2020 23:46:22 -0500
> > >>
> > >> Here is the cgrep script:
> > >>
> > >> #!/bin/bash
> > >>
> > >> grep -a "$@" | cut -c -200
> > >>
> > >> cut seems to be responsible for the problem by buffering output even to a tty.
> > >
> > > Sounds like a useful feature to ask Grep developers to add it.
> >
> > That feature already exists: stdbuf.
>
> I'm not sure I understand: I meant the feature to limit the output
> lines to a given column count.
Is it not this option for limiting?
-m NUM, --max-count=NUM
Stop reading a file after NUM matching lines. If the
input is standard input from a regular file, and NUM
matching lines are output, grep ensures that the
standard input is positioned to just after the last
matching line before exiting, regardless of the
presence of trailing context lines. This enables a
calling process to resume a search. When grep stops
after NUM matching lines, it outputs any trailing
context lines. When the -c or --count option is also
used, grep does not output a count greater than NUM.
When the -v or --invert-match option is also used, grep
stops after outputting NUM non-matching lines.
next prev parent reply other threads:[~2020-11-30 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 5:22 bug#44941: 28.0.50; M-x grep, perhaps all asynch subprocesses Richard Stallman
2020-11-29 5:39 ` Drew Adams
2020-11-29 5:41 ` Drew Adams
2020-11-29 10:47 ` Lars Ingebrigtsen
2020-11-29 15:29 ` Eli Zaretskii
2020-11-30 4:46 ` Richard Stallman
2020-11-30 9:29 ` Lars Ingebrigtsen
2020-11-30 15:41 ` Eli Zaretskii
2020-11-30 15:47 ` Andreas Schwab
2020-11-30 16:38 ` Eli Zaretskii
2020-11-30 16:46 ` Jean Louis [this message]
2020-11-30 18:04 ` Eli Zaretskii
2020-12-01 5:23 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X8Uh5APCdfVsjW0u@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=44941@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).