From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Michael O'Brien" <mobrien@pixar.com>
To: <earnie_boyd@yahoo.com>, "Bob McGowan" <rmcgowan@veritas.com>, <cygwin@sourceware.cygnus.com>
Subject: Re: odd sed behavior
Date: Wed, 22 Mar 2000 10:08:00 -0000
Message-id: <006701bf9429$80ee63e0$0a32a8c0@rainsound.com>
References: <20000322175103.8785.qmail@web113.yahoomail.com>
X-SW-Source: 2000-03/msg00535.html

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 <earnie_boyd@yahoo.com>
To: Michael O'Brien <mobrien@pixar.com>; Bob McGowan <rmcgowan@veritas.com>;
<cygwin@sourceware.cygnus.com>
Sent: Wednesday, March 22, 2000 9:51 AM
Subject: Re: odd sed behavior


> --- Michael O'Brien <mobrien@pixar.com> 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: < mailto:earnie_boyd@yahoo.com >
>             __Cygwin: POSIX on Windows__
> Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
>            __Minimalist GNU for Windows__
>   Mingw32 List: < http://www.egroups.com/group/mingw32/ >
>     Mingw Home: < http://www.mingw.org/ >
>
> __________________________________________________
> 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@sourceware.cygnus.com