Date: Thu, 1 Nov 2001 16:12:32 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Guido van Rooij <guido@gvr.org> Cc: Dag-Erling Smorgrav <des@ofug.org>, "Eugene L. Vorokov" <vel@bugz.infotecs.ru>, freebsd-hackers@freebsd.org Subject: Re: buildworld breakage during "make depend" at usr.bin/kdump Message-ID: <20011101161231.D30776@student.uu.se> In-Reply-To: <20011101133624.A12072@gvr.gvr.org> References: <200111011135.fA1BZwh54619@bugz.infotecs.ru> <xzpd732vhra.fsf@flood.ping.uio.no> <20011101132830.A11708@gvr.gvr.org> <xzp4roevflt.fsf@flood.ping.uio.no> <20011101133624.A12072@gvr.gvr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 01, 2001 at 01:36:24PM +0100, Guido van Rooij wrote:
> On Thu, Nov 01, 2001 at 01:29:50PM +0100, Dag-Erling Smorgrav wrote:
> > Guido van Rooij <guido@gvr.org> writes:
> > > May I aks which shell you are using?
> >
> > Zsh.
>
> I am starting to wonder which sh is broken.....
Neither really. First note that zsh doesn't claim to be fully compatible with
/bin/sh (or POSIX-compliant for that matter.) Secondly, zsh has a lot
of options defining how it works. In this case the option
SH_WORD_SPLIT defines which behaviour will be used. If this option is
set it will replace the newline with a space. If it is not set (which
is the default) the newline will be retained as it is.
>
> Btw there is a difference between sh and {t,}csh: in the sh case the newline
> is replaced with 1 space. In the case of the 2 others, there are 2 spaces.
--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011101161231.D30776>