Date: Thu, 16 Aug 2001 22:00:01 -0700 (PDT) From: Jeremy Chadwick <yoshi@parodius.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/29790: sed "G" command broken Message-ID: <200108170500.f7H501945318@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/29790; it has been noted by GNATS. From: Jeremy Chadwick <yoshi@parodius.com> To: Mike Heffner <mheffner@vt.edu> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/29790: sed "G" command broken Date: Thu, 16 Aug 2001 21:51:33 -0700 Yes, I just noticed this as well. According to the documentation, the way it's *supposed* to work is as follows: $ cat > file one two three four five $ sed "1,2H;3G" file one two three one two four five $ However, the present sed implementation does the following: $ sed "1,2H;3G" file one two three one two four five Note the lack-of newline between "three" and "one". My previous example (re: printf | sed) works as well. :-) On Fri, Aug 17, 2001 at 12:43:42AM -0400, mheffner@novacoxmail.com wrote: > Hrm, after applying the patch and rebuilding sed I don't see any difference in > the example you provided (ie. both print the 'wrong' output you posted). I know > very little about sed, but is there a bug in the example you provided? 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?200108170500.f7H501945318>