Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-VirusChecked: Checked X-Env-Sender: okiddle@yahoo.co.uk X-Msg-Ref: server-3.tower-36.messagelabs.com!1080639168!5006381 X-StarScan-Version: 5.2.10; banners=-,-,- X-Originating-IP: [158.234.9.163] Cc: zzapper , zsh-workers@sunsite.dk, cygwin@cygwin.com X-VirusChecked: Checked X-StarScan-Version: 5.0.7; banners=.,-,- In-reply-to: From: Oliver Kiddle References: <1vvf60l9i7n4nlobcroik2le5ofe6v2rn4@4ax.com> To: "Peter A. Castro" Subject: Re: zsh and line breaks Date: Tue, 30 Mar 2004 11:32:02 +0200 Message-ID: <3372.1080639122@trentino.logica.co.uk> "Peter A. Castro" wrote: > > I run zsh on Cygwin, unlike bash zsh gets very upset if it sees dos > > returns. I have to run dos2unix on my zsh scripts. > > > > I haven't seen an explanation for this > > Hmm... I'll have to look into this. I thought I'd corrected this for > Cygwin... Are those corrections likely to be limited to the Cygwin package for zsh? I don't use Cygwin myself but from a quick search, it looks like there is an O_TEXT flag to open which we could use (a couple of places in init.c would cover scripts I think). Wouldn't work where the script comes from stdin, though. Does that perhaps help? Oliver -- 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/