public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mikhail Usenko <cygwin@inbox.ru>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: bash-4.3.42-3
Date: Fri, 11 Sep 2015 17:21:00 -0000	[thread overview]
Message-ID: <20150911202057.c8b93859ae3443187483f2fc@inbox.ru> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E91BBF5@USA7109MB022.na.xerox.net>

On Fri, 11 Sep 2015 12:48:59 +0000
Nellis, Kenneth <...> wrote:

> 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
> 

Hello, Ken.
Thank you for the notice about that thread. I didn't know about it.
As far as I understand that conversation, Paolo Bonzini changed the default open mode from 'rt' to 'r'.
And as it can be observed from the sed's sources now there are to variants for the value of the
global variable that is used to set file open mode for all read operations: "r" by default and "rb"
if the -b command flag is set.

So there is no text mode forcing as it has been and it is up to the underlying Cygwin level
in which actual mode the file to be opened. I suppose a package maintainer can also choose
which specific Cygwin library the application can be linked against to set the default open modes for it.

We have a shell pipeline here (basically it is a pipe or a FIFO file) which is normally expected to be opened in binary mode (and according to Cygwin user's guide pipes, sockets and non-file devices are opened in binary mode). Therefore I think it looks like a bug.

-- 
Mike

--
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

      reply	other threads:[~2015-09-11 17:21 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
2015-09-11 17:21     ` Mikhail Usenko [this message]

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=20150911202057.c8b93859ae3443187483f2fc@inbox.ru \
    --to=cygwin@inbox.ru \
    --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).