From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated [test]: sed-4.4-1
Date: Sun, 12 Feb 2017 15:13:00 -0000 [thread overview]
Message-ID: <58a07b9b.085fca0a.8af3f.103c@mx.google.com> (raw)
In-Reply-To: <20170212113222.GF11666@calimero.vinschen.de>
On Sun, 12 Feb 2017 12:32:22, Corinna Vinschen wrote:
> awk is used to manipulate text input in the first place so it treats all
> input, files as well as stdin, as text. So, shall we drop this
> behaviour for files only? Or for stdin as well? How many existing
> setups are bound to fail after a change?
Perhaps I am missing something, but cant all that be said about Sed too? I just
cant see a situation where we are justified changing one and not the other. They
should either both strip carriage returns or neither.
--
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:[~2017-02-12 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 17:20 Eric Blake (cygwin)
2017-02-11 23:01 ` Steven Penny
2017-02-12 11:32 ` Corinna Vinschen
2017-02-12 15:13 ` Steven Penny [this message]
2017-02-13 14:15 ` Nellis, Kenneth (Conduent)
2017-02-13 15:53 ` cyg Simple
2017-02-13 19:07 ` Eric Blake
2017-02-13 19:15 ` Eric Blake
2017-02-16 5:05 ` Steven Penny
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=58a07b9b.085fca0a.8af3f.103c@mx.google.com \
--to=svnpenn@gmail.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).