Return to BSD News archive
Xref: sserve comp.unix.user-friendly:2822 comp.unix.solaris:22102 comp.unix.programmer:19672 comp.unix.misc:13718 comp.unix.aux:15266 comp.unix.bsd:14777 comp.unix.aix:43359 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!EU.net!uknet!warwick!not-for-mail From: cudcv@csv.warwick.ac.uk (Rob McMahon) Newsgroups: comp.unix.user-friendly,comp.unix.solaris,comp.unix.programmer,comp.unix.misc,comp.unix.aux,comp.unix.bsd,comp.unix.aix Subject: Re: Shell wars Date: 30 Aug 1994 16:29:17 +0100 Organization: University of Warwick, Coventry, UK Lines: 21 Distribution: inet Message-ID: <33vj8d$b4i@sprocket.csv.warwick.ac.uk> References: <33af70$8rd@usenet.INS.CWRU.Edu> <33gvms$56a@wombat.cssc-syd.tansu.com.au> <33jk6l$6cq@hamlet.umd.edu> <CHRISB.94Aug29144419@wombat.cssc-syd.tansu.com.au> NNTP-Posting-Host: sprocket.csv.warwick.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In article <CHRISB.94Aug29144419@wombat.cssc-syd.tansu.com.au>, chrisb@wombat.cssc-syd.tansu.com.au (Chris Bitmead) writes: >I'll be the first to back up BSD in many areas, but csh would not be one of >them. The design flaws in csh are well documented. What is it that you can do >in csh that you can't do in the bourne flavoured shells? The thing I really miss in sh is set lpargs = ( $lpargs:q $nextarg:q ) i.e. some decent way of forming lists without causing problems with spaces, quotes, and backslashes. Lists are useful throughout csh, and there really is no good substitute in sh. Cheers, Rob -- UUCP: ...!mcsun!uknet!warwick!cudcv PHONE: +44 203 523037 INET: cudcv@csv.warwick.ac.uk Rob McMahon, Computing Services, Warwick University, Coventry CV4 7AL, England