This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: zsh and line breaks
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 6 Apr 2004 10:38:06 +0200
- Subject: Re: zsh and line breaks
- References: <1040403203504.ZM15601@candle.brasslantern.com> <20040404192948.8E1978545@pwstephenson.fsnet.co.uk>
- Reply-to: cygwin at cygwin dot com
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@cygwin.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/