Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 19 Feb 2004 19:52:50 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: search and replace tool In-Reply-To: <40355763.E01A2710@dessent.net> Message-ID: References: <291592011.20040218205953@thequod.de> <6.0.1.1.0.20040218151724.0398d488@127.0.0.1> <40354B21.6040802@x-ray.at> <40355763.E01A2710@dessent.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Thu, 19 Feb 2004, Brian Dessent wrote: > Igor Pechtchanski wrote: > > > On Fri, 20 Feb 2004, Reini Urban wrote: > > > > > But fixing perl's long-standing inability to do direct inline editing > > > via perl -i would be cygwin specific. > > > Anyone investigated this lately? > > > > What on Earth are you talking about? What inability? WFM (see below). > > ... > > $ perl -i -pe 's/blah/stuff/g' sometext > > $ ls > > sometext sometext.bak > > It didn't do the editing "inline", it created a new file and renamed the > old one ".bak". In other words, on Cygwin "-i" is really "-i.bak". If > you try the above sequence on linux you don't get a .bak file and the > changes are truly done in-place. I assume this relates to differences > in filesystem semantics. > > Brian I stand corrected. Thanks for the explanation. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/