Date: Sun, 13 Mar 2005 02:20:05 GMT From: Giorgos Keramidas <keramida@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/78692: [PATCH] add support for line buffered output to sed(1) Message-ID: <200503130220.j2D2K5MC092981@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/78692; it has been noted by GNATS. From: Giorgos Keramidas <keramida@freebsd.org> To: Eugene Grosbein <eugen@kuzbass.ru> Cc: bug-followup@freebsd.org Subject: Re: bin/78692: [PATCH] add support for line buffered output to sed(1) Date: Sun, 13 Mar 2005 04:16:42 +0200 On 2005-03-11 18:31, Eugene Grosbein <eugen@kuzbass.ru> wrote: > --- usr.bin/sed/sed.1.orig Fri Mar 11 18:27:47 2005 > +++ usr.bin/sed/sed.1 Fri Mar 11 18:29:37 2005 > @@ -43,11 +43,11 @@ > .Nd stream editor > .Sh SYNOPSIS > .Nm > -.Op Fl Ean > +.Op Fl Ealn > .Ar command > .Op Ar > .Nm > -.Op Fl Ean > +.Op Fl Ealn > .Op Fl e Ar command > .Op Fl f Ar command_file > .Op Fl i Ar extension > @@ -109,6 +109,8 @@ > .Ar extension > when in-place editing files, as you risk corruption or partial content > in situations where disk space is exhausted, etc. > +.It Fl l > +Make stdout line buffered. Hi, "stdout" is something that depends on an understanding of how stdio.h works in ANSI C. Since the executable of sed is pretty much language-agnostic and we can't expect all the users of FreeBSD to be C programmers, I'd probably write this as: .It Fl l Make output line buffered. Other than this minor detail, the manpage diff looks fine (as long as we don't forget to bump the date too when it is committed).home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503130220.j2D2K5MC092981>