From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 44941@debbugs.gnu.org, 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 20:04:05 +0200 [thread overview]
Message-ID: <83eekak9gq.fsf@gnu.org> (raw)
In-Reply-To: <X8Uh5APCdfVsjW0u@protected.rcdrun.com> (message from Jean Louis on Mon, 30 Nov 2020 19:46:28 +0300)
> Date: Mon, 30 Nov 2020 19:46:28 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Andreas Schwab <schwab@linux-m68k.org>, 44941@debbugs.gnu.org,
> rms@gnu.org
>
> > > >> 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
No. Please read the 'cut' documentation to see what does -c do there.
next prev parent reply other threads:[~2020-11-30 18:04 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
2020-11-30 18:04 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eekak9gq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44941@debbugs.gnu.org \
--cc=bugs@gnu.support \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.