From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] Updated: bash-4.3.42-3
Date: Fri, 11 Sep 2015 12:49:00 -0000 [thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A702E91BBF5@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <20150911141729.0318b690929d91edcee250bd@inbox.ru>
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
next prev parent reply other threads:[~2015-09-11 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 21:17 Eric Blake (cygwin)
2015-09-11 11:17 ` Mikhail Usenko
2015-09-11 12:49 ` Nellis, Kenneth [this message]
2015-09-11 17:21 ` Mikhail Usenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D835E9B9CD07F40A48423F80D3B5A702E91BBF5@USA7109MB022.na.xerox.net \
--to=kenneth.nellis@xerox.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).