Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Sat, 4 Dec 2004 11:30:54 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: sed: altered results in bash and cmd Message-ID: <20041204163054.GC15990@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <41B19CA6 DOT 6090203 AT schoenhaber DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sat, Dec 04, 2004 at 03:04:52PM +0100, Jan Schormann wrote: >> C:\>E:\cygwin\bin\echo.exe '/^ .*$/d' >> / .*$/d > >>I'm not really sure but I think cmd doesn't treat single quotes as >>quoting characters - at least not in the way bash does. > >That's true. In addition, the '^' in cmd is an escape character, like >the backslash in sh. Search for "string literals" in the XP help and >support center. cmd may not treat single quotes as quoting characters but cygwin does when a command is started from the windows command prompt. As has been noted, the ^ is being eaten by cmd before cygwin ever sees it. 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/