Date: Mon, 1 Jul 2002 17:34:03 -0700 (PDT) From: Rob Anderson <rob@isilon.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/40101: sed buffers one line of output before writing to stdout Message-ID: <200207020034.g620Y3As080655@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 40101 >Category: bin >Synopsis: sed buffers one line of output before writing to stdout >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jul 01 17:40:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Rob Anderson >Release: 4.5-STABLE >Organization: Isilon Systems Inc. >Environment: FreeBSD beasly.isilon.com 4.5-STABLE FreeBSD 4.5-STABLE #3: Thu Apr 18 15:58:15 PDT 2002 toor@beasly.endurantsystems-internal.com:/usr/src/sys/compile/ROB i386 >Description: sed buffers a full line before writing to stdout. For example, if I enter "sed 's/foo/bar/'" at the prompt, I get the following interaction: blah <--- I enter this, get no response foobar <--- I enter this... blah <--- suddenly, the response to my 'blah' is printed stuff <--- I enter this... barbar <--- now, the response to 'foobar' is printed This is _not_ the behavior in Linux sed...Linux sed prints out every line as it is processed. 'perl -pe' also prints out lines as they are processed. Only BSD sed exhibits this property. I couldn't find anything in the manpage that explains why BSD sed behaves this way. >How-To-Repeat: See above... repeats every time. Just run sed with any command, and you'll get this behavior. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207020034.g620Y3As080655>