GNU bug report logs - #35339
Say what buffering is not --line-buffered

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35339 in the body.
You can then email your comments to 35339 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-grep <at> gnu.org
Subject: Say what buffering is not --line-buffered
Date: Sat, 20 Apr 2019 19:41:44 +0800

On (info "(grep) Other Options")

  ‘--line-buffered’
       Use line buffering on output.  This can cause a performance
       penalty.

OK, but say what will happen if one doesn't use this. Paragraph
buffering? Page buffering?

Message #10 received at 35339-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 35339-done <at> debbugs.gnu.org
Subject: Re: bug#35339: Say what buffering is not --line-buffered
Date: Tue, 22 Sep 2020 11:00:15 -0700

[Message part 1 (text/plain, inline)]

On 4/20/19 4:41 AM, 積丹尼 Dan Jacobson wrote:
>    ‘--line-buffered’
>         Use line buffering on output.  This can cause a performance
>         penalty.
> 
> OK, but say what will happen if one doesn't use this. Paragraph
> buffering? Page buffering?

Thanks for mentioning this. I installed the attached patch to try to clarify 
this point.

[0001-doc-improve-line-buffer-doc.patch (text/x-patch, attachment)]

Previous Next

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