Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <006701bf9429$80ee63e0$0a32a8c0@rainsound.com> Reply-To: "Michael O'Brien" From: "Michael O'Brien" To: , "Bob McGowan" , References: <20000322175103 DOT 8785 DOT qmail AT web113 DOT yahoomail DOT com> Subject: Re: odd sed behavior Date: Wed, 22 Mar 2000 10:07:34 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Hola~ This is what I'm doing currently. The sed expression is in a Makefile, so the better solutution would be to leave it there as opposed to adding a two line file. I'm not trying to be picky, I just want to understand who's having problems (sed or the command prompt). MO ----- Original Message ----- From: Earnie Boyd To: Michael O'Brien ; Bob McGowan ; Sent: Wednesday, March 22, 2000 9:51 AM Subject: Re: odd sed behavior > --- Michael O'Brien wrote: > > Hola~ > > > > The command below does work using bash. However, I'm not using bash, but the > > command prompt. I agree with the diagnosis that the problem lies in the ". I > > really need a work around, tho. > > > > [edit] foo.sed > s/[\\"]/\\&/g > s/.*/\"&\",/ > > [dos_prompt] sort -u foo.file | sed -f foo.sed > > [caveat emptor] Untested. > > Regards, > > > ===== > --- > Earnie Boyd: > __Cygwin: POSIX on Windows__ > Cygwin Newbies: > __Minimalist GNU for Windows__ > Mingw32 List: > Mingw Home: > > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com