X-Spam-Check-By: sourceware.org Date: Tue, 12 Dec 2006 00:40:03 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: recent popen changes Message-ID: <20061212054003.GA8169@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <457E2438 DOT 5060005 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <457E2438.5060005@byu.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Dec 11, 2006 at 08:38:32PM -0700, Eric Blake wrote: >Any reason that cygwin can't support popen("echo hi", "rb") to force >binary pipe traffic, or conversely, popen("echo hi", "rt") to force >text pipe traffic? True, POSIX states that any characters after the >first can result in EINVAL, but now that cgf just rewrote popen to be >more efficient, it would be nice to specify the binary mode up front >rather than relying on CYGWIN=nobinmode or having to use setmode after >the fact. Sure, I could do that. I'll check in something tomorrow. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/