X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Sat, 24 Apr 2010 13:08:33 +0300 From: Eli Zaretskii Subject: Re: GNU sed question In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83mxwt17tq.fsf@gnu.org> References: <4c64a5b1-bf8a-49e1-843e-9a0594856e82 AT c36g2000yqm DOT googlegroups DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Rod Pemberton" > Date: Sat, 24 Apr 2010 03:36:54 -0400 > Bytes: 2064 > > "Rugxulo" wrote in message > news:4c64a5b1-bf8a-49e1-843e-9a0594856e82 AT c36g2000yqm DOT googlegroups DOT com... > > > > P.S. I love GNU sed, but in my experience it's pretty darn > > slow on big files. > > > > I've not used it. I have need of VI, occasionally. I prefer DOS EDIT, but > it and other DOS editors seem unable to do two things that VI can do. VI and EDIT are unrelated to Sed. Sed is a _stream_ editor, it edits files in batch mode, not interactively. It is suitable for scripts that need to edit text. Sed's slowness is generally due to GNU regex library (assuming that is used for building the DJGPP port). In the past, building Sed with DJGPP's native regex routines produced a much faster Sed.