|
From: Earnie B. <ear...@ya...> - 2002-03-31 16:30:28
|
On 3/30/2002 at 9:17 PM Andrew Begel wrote: >There's something funny going on with sed in MSYS 1.0.6. > > >After some experimentation, it does appear to be completely related to >the line endings in the file. If the source file has DOS line endings >\r\n, sed doesn't properly find regexps that occur at the end of the >line ($); if the source file has unix line endings, even MSYS' sed >behaves properly. > Hmm... I'll have to take a look at the sed source and fix it for \r\n line endings. Thanks for the report. In the meantime perhaps a preliminary regexp of '\r$' would help. I first thought you were going to report something I found yesterday with the "XP For Home" OS and sed. The following doesn't seem to want to work: `echo $COMSPEC | sed -e 's#\\#/#g#'` The result is that I get the \ version returned. I can make it work on the command line but not in the evaluated script. I'll have to research this some more also. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |