- Original Message -
From: "Dwight Neal" <[EMAIL PROTECTED]>
To: "'Peter S Tillier'" <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 11:05 PM
Subject: RE: Sed Script works in 3.02-1, fails in 4.0.1-1
> I included the WRONG sed script w
- Original Message -
From: "Randall R Schulz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 10, 2003 4:30 PM
Subject: Re: FW: Sed Script works in 3.02-1, fails in 4.0.1-1
> Dwight,
>
> I can reproduce your problem using sed 4.0.1, as
Dwight,
I can reproduce your problem using sed 4.0.1, assuming sed actually gets
some input (if there's no input on standard input, the diagnostic does not
occur). Changing the pattern separators does not cure the problem.
Replicating the address range pattern ("<.BLOCKQUOTE>") in the empty
su
Title: FW: Sed Script works in 3.02-1, fails in 4.0.1-1
I included the WRONG sed script with the original message.
Attached is the correct one--that is, the one that creates the fuss--, with the (obviously) missing RE.
Sorry to waste your time on that--I had been doing a lot of
- Original Message -
From: "Dwight Neal" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 7:33 PM
Subject: Sed Script works in 3.02-1, fails in 4.0.1-1
> I am migrating from a machine that uses a cygwin image loaded in May
2002 to
&
Dwight,
I can't tell what you intend to do with that SED script, but I agree with
its complaint.
If you want to use slashes within the pattern or replacement, you'll either
have to escape them by preceding each with a backslash or use an
alternative separator. I'm fond of semicolon in this kin
Title: Sed Script works in 3.02-1, fails in 4.0.1-1
I am migrating from a machine that uses a cygwin image loaded in May 2002 to one that uses a November 2002 download, and have a sed script that fails in the newer version:
(This should be a single line of input, but I'm sure it will
7 matches
Mail list logo
