[ANNOUNCEMENT] Updated: bash-4.3.42-3
Nellis, Kenneth
Kenneth.Nellis@xerox.com
Fri Sep 11 12:49:00 GMT 2015
From: Mikhail Usenko
<snip>
> There is also the similar problem found accidentally just now with sed in
> pipelines:
> $ echo -ne "\r\n" | sed '' | od -A n -tx1 # should be: 0d 0a
> 0a
> $ echo -ne "\r\r\n" | sed '' | od -A n -tx1 # should be: 0d 0d 0a
> 0d 0a
FWIW, back in 2012 there was a discussion on this behavior of sed.
Apparently strong enough arguments were made to retain this behavior.
http://sourceware.org/ml/cygwin/2012-02/msg00301.html
--Ken Nellis
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list