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: Wed, 22 May 2002 17:02:33 -0700 (PDT) From: "Peter A. Castro" To: Matthew Smith cc: cygwin-apps AT cygwin DOT com Subject: Re: new package offering: zsh In-Reply-To: <01ea01c201e8$e302d7d0$010a10ac@bluesguitar.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 22 May 2002, Matthew Smith wrote: > I'll vote "yes" for this, but I do have a question: have you dealt with > binary/text issues specific to the windows platform in your port? I know of one issue concerning loading of functions. Is there another you had in mind? For the most part, zsh handles cr+lf as if it were lf implicitly. For loading functions, the code assumes a binary mode, ie: the number of bytes reported by stat() of a file is the number of bytes reported back from read() after reading in the whole file. On a filesystem mounted in textmode, this isn't always true and can cause the function to not load. I really feel this is a filesystem attribute issue, but if it's annoying enough for people, I'll loosen the size matching restrictions. A workaround for now is to strip your functions of all Carriage-Returns, thus only have linefeeds in the file. > cheers, > -Matt > > > Hi All, > > In doing porting work for another project, I ended up porting zsh (my > > favorite shell) to Cygwin, so I might as well offer it as a package. I > > will be an active maintainer of zsh as I use this shell on a regular bases > > on many systems. Here's the setup.hint and all the URLs: -- Peter A. Castro or "Cats are just autistic Dogs" -- Dr. Tony Attwood