sed and find
Larry Hall (RFK Partners, Inc)
Thu Nov 16 09:42:00 GMT 2000
At 11:53 AM 11/16/2000, Armin Theissen wrote:
>I'm new to this list and to cygwin in general, and I have a problem
>which I cannot find discussed anywhere on the faq or mailing list
>its about the commands 'sed' and 'find'. I used the cygwin_b20 and
>their sed and find therein with no problems, but the obviously
>different sed and find in cygwin 1.1.4 gives me compile errors.
>sed complains about unterminated 's' commands, as in
> sed "s/bla/blubb/"
>which can there be solved by removing the quotation marks. However,
>in order to expand complicated s/// expressions when compiling under
>non windows plattforms, I cannot simply remove them all in the (huge)
>code. Is there a way to make sed in cygwin 1.1.4 understand the
>Another cause for headaches is 'find' which just won't find anything but
>complains about unfound files/directories - as it seems in the path
>where to find. I assume there is a problem with slashes and backslashes.
>Again, the find of cygwin b20 worked.
Generally these kinds of problems are due to carriage returns in files,
although the bash and ash versions that come with 1.1.4 should be much better
at making this issue transparent. Make sure you're up-to-date here. The
more recent, the better! As a last resort, you can certainly run your
files through "tr" to remove the carriage returns. To do further analysis
of your configuration, we'd need the output of cygcheck -s -r -v though.
>Is there any chance to get these working without copying over the old
>versions? Or is this eventually a known bug for which there is somewhere
>here a solution?
>I hope there is. Otherwise: will cygwin_b20 still be available in the
Absolutely not. B20 is unsupported now.
Larry Hall email@example.com
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org
More information about the Cygwin