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 Date: Tue, 6 Apr 2004 10:38:06 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: zsh and line breaks Message-ID: <20040406083806.GJ26575@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1040403203504 DOT ZM15601 AT candle DOT brasslantern DOT com> <20040404192948 DOT 8E1978545 AT pwstephenson DOT fsnet DOT co DOT uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040404192948.8E1978545@pwstephenson.fsnet.co.uk> User-Agent: Mutt/1.4.2i On Apr 4 20:29, Peter Stephenson wrote: > Bart Schaefer wrote: > > On Apr 2, 5:23pm, Peter A. Castro wrote: > > } > > } On Thu, 1 Apr 2004, Peter A. Castro wrote: > > } > > } So, now I need a ruling on just where to put this fix. > > > > I don't know that I can give you a "ruling" but in my opinion it would be > > fine to put this in main.c, appropriately #ifdef'd. > > I agree, there's nothing magic about main.c. The only reason it's short > is because usually it's convenient for as much stuff as possible to be > in zsh.dll, on systems where that needs to exist. Your case is exactly > the opposite, so main.c is fine. I'm wondering if it makes sense to add a "/usr/lib/textreadmode.o" to Cygwin, so that applications like zsh and gawk don't have to have this code to provide by themselves. A simple case "$host" in *-*-cygwin*) LIBS="$LIBS /usr/lib/textreadmode.o";; esac in configure.ac would do it then. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/