X-Spam-Check-By: sourceware.org Date: Wed, 18 Jul 2007 18:41:09 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: problem with "sed" on cygwin...duplicable? Message-ID: <20070718224109.GB17624@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <469E9423 DOT 1020506 AT tlinx DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <469E9423.1020506@tlinx.org> User-Agent: Mutt/1.5.15 (2007-04-06) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Jul 18, 2007 at 03:28:51PM -0700, Linda Walsh wrote: > I was wondering if the following simple example worked for > other people. It works on my linux box, but not on my cygwin > box. > > Fails & prints usage: > > echo 1|sed -r 's/1/2/' > > The problem seems to be the extended regular expression switch. > The spelled out form was no better. You probably have another version of sed in your path then. WJFFM. cygcheck output would also tell us if you have the right version of sed. cgf -- 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/