Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: cygwin AT cygwin DOT com From: zzapper Subject: Re: [ANNOUNCEMENT] Updated: zsh-4.2.0-2 Date: Thu, 08 Apr 2004 11:31:52 +0100 Lines: 31 Message-ID: References: <20040407152041 DOT AF6F5400155 AT timesys DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: cpc3-oxfd4-4-0-cust194.oxfd.cable.ntl.com X-Newsreader: Forte Free Agent 1.93/32.576 English (American) On Wed, 7 Apr 2004 11:20:41 -0400 (EDT), wrote: >An updated version of zsh (zsh-4.2.0-2) has been released and should be >at a mirror near you real soon. > >- Fix for running scripts from text-mode mounted filesystems. Previously > if you ran a script from a text-mode mount, and it had DOS CR/LF's line > termination, zsh would report ^M errors. The shell now opens such > files with O_TEXT which causes line termination to be massaged. I'll > be watching for problem reports concerning this as it was a broad > change, the implications of which haven't been fully realized yet. > Peter, I think this is a really useful problem to resolve for the popolarity of zsh on cygwin. Many of us are fairly impatient, and think well I've got 30 minutes; I'll give zsh a go, then try to convert an existing bash script get these ^M problems and think blast I have to rewrite my existing scripts, decide they haven't got time for that and give up. (Your bash scripts should all work under zsh; In any case you can choose to leave the shebang as #!/bin/bash) Anyway thanks again zzapper (vim, cygwin, wiki & zsh) -- vim -c ":%s/^/WhfgTNabgureRIvzSUnpxre/|:%s/[R-T]/ /Ig|:normal ggVGg?" http://www.vim.org/tips/tip.php?tip_id=305 Best of Vim Tips -- 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/