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 Message-ID: <021801c201f2$8e241d00$010a10ac@bluesguitar.org> From: "Matthew Smith" To: "Peter A. Castro" Cc: References: Subject: Re: new package offering: zsh Date: Wed, 22 May 2002 19:41:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 This sounds perfectly reasonable to me. cheers, -Matt > 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. >