Date: Mon, 22 Mar 1999 10:50:04 +0800 (CST) From: Scott Hazen Mueller <scott@zorch.sf-bay.org> To: mkb@altair.mayn.de, freebsd-bugs@freebsd.org Subject: Re: bin/10720: bug in sed context address handling Message-ID: <199903220250.KAA07518@zork.sf-bay.org>
index | next in thread | raw e-mail
Then I guess I'll have to file a doco bug report, because the meaning of that sentence is far from clear. >From mkb@altair.mayn.de Mon Mar 22 10:46:13 1999 >From: Matthias Buelow <mkb@altair.mayn.de> >Date: Mon, 22 Mar 1999 03:41:08 +0100 >To: scott@zorch.sf-bay.org >Cc: freebsd-bugs@freebsd.org >Subject: Re: bin/10720: bug in sed context address handling >Message-Id: <199903220241.DAA14820@altair.mayn.de> >Content-Type: text/plain; charset=us-ascii >Mime-Version: 1.0 >Scott Hazen Mueller <scott@zorch.sf-bay.org> wrote: >>>Number: 10720 >>>Synopsis: bug in sed context address handling >> >>According to sed(1) >> >> A command line with two addresses selects the inclusive range from the >> first pattern space that matches the first address through the next pat- > ^^^^ >> tern space that matches the second. (If the second address is a number >"Next" is the keyword here. Sed is behaving correctly as documented >(the Digital UNIX sed has the same "quirk", btw.) >The first address matches the entire line, then sed reads in the next >and starts looking for the second match. Since none is found, it selects >all until the end of file. > - mkb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903220250.KAA07518>