public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bob McGowan <rmcgowan@veritas.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: odd sed behavior
Date: Tue, 21 Mar 2000 18:27:00 -0000	[thread overview]
Message-ID: <38D83113.476DA178@veritas.com> (raw)
In-Reply-To: <20000321203229.C22262@cygnus.com>

Chris Faylor wrote:
> 
> On Tue, Mar 21, 2000 at 05:14:28PM -0800, Michael O'Brien wrote:
> >When using the 20.1 version of cygwin, I'm seeing the following
> >strange-ness. From the command prompt:
> >
> >    F:\>sort  -u  a.msg  |  sed 's/[\\"]/\\&/g;s/.*/\"&\",/'
> >    sed: -e expression #1, char 21: Unterminated `s' command
> >    The system cannot find the path specified.
> >
> >    F:\>sort  -u  a.msg  |  sed 's/[\\"]/\\&/g;s/.*/&,/'
> >
> >Anyone have any ideas why this doesn't work?
> 
> I don't believe that B20.1 understands the "'" (apostrophe) quote
> character.
> 
> cgf
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

This is a command prompt (not bash) issue, I believe.  The Windows
command prompt does not use the single quote (apostrophe) for quoting,
only double quotes.  The single quotes are probably being passed in to
sed.

I'd suggest to Michael that you try first starting the bash shell, then
run the sed command and see what happens.

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-03-21 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-21 17:15 Michael O'Brien
2000-03-21 17:32 ` Chris Faylor
2000-03-21 18:27   ` Bob McGowan [this message]
2000-03-21 18:33     ` Chris Faylor
2000-03-22  9:33     ` Michael O'Brien
2000-03-22  9:51 Earnie Boyd
2000-03-22 10:08 ` Michael O'Brien
2000-03-22 10:16 Earnie Boyd
2000-03-22 11:26 ` Chris Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38D83113.476DA178@veritas.com \
    --to=rmcgowan@veritas.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).