Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Thu, 23 May 2002 11:11:41 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <10404879856.20020523111141@logos-m.ru> To: "Peter A. Castro" CC: Charles Wilson , Matthew Smith , Subject: Re: new package offering: zsh In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Thursday, 23 May, 2002 Peter A. Castro doctor AT fruitbat DOT org wrote: PAC> On Wed, 22 May 2002, Charles Wilson wrote: >> No -- if zsh can handle cr+lf internally, then let it do so. Explicitly >> open function files in binary mode -- this will override the "textmode >> mount" which sets the default read mode. PAC> zsh uses the open() call, not fopen(). There is no "binary" vs. "text" PAC> mode to specify. Theoretically, open() should be opening the file in PAC> binary mode already (ie: no text translation/interpretation), yet the PAC> data read in clearly is being cooked under some scenarios. No, if I PAC> understand how things are work here, I believe the carriage control PAC> processing is being done at the filesystem level, which is below open() PAC> and beyond my control. It is under your control. You can use setmode () function on file descriptor. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19