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 kind of situation.
Randall Schulz
At 11:33 2003-01-08, Dwight Neal wrote:
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 wrap when emailed):
sed -f modifyhtm.txt "\Web Configuration\Default_installing.htm" >results\Default_installing.htm
The error reported is:
'sed: file modifyhtm.txt line 1: No previous regular expression'
The only difference I can find between the two machines (both WinXP, similar hardware, etc) is that I have sed 4.0.1-1 on the newer one. When I back off to the older sed.exe, the script runs just fine. I use about 30 other scripts on the two machines without errors.
I am attaching cygcheck -s output from each machine (before I made any changes to executables), and the modifyhtm.txt script. The one caveat: the output from the ver 4 machine shows I had a CYGWIN environment variable set to binmode, but this was for testing, and did not effect the outcome.
Thanks for your help,
Dwight Neal
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
