From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8017 invoked from network); 16 Sep 2002 22:06:30 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 16 Sep 2002 22:06:30 -0000 Received: (qmail 16069 invoked by alias); 16 Sep 2002 22:06:13 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5355 Received: (qmail 16057 invoked from network); 16 Sep 2002 22:06:12 -0000 From: Bruce Stephens To: "Zsh-Users (E-mail)" Subject: Re: What is the zsh equivalent of csh's set echo? References: <1F1D28572ECAD211BC490008C75D71F5025D6388@NPRI54EXC18.NPT.NUWC.NAVY.MIL> Date: Mon, 16 Sep 2002 23:06:11 +0100 In-Reply-To: <1F1D28572ECAD211BC490008C75D71F5025D6388@NPRI54EXC18.NPT.NUWC.NAVY.MIL> (Hall Jeffrey S NPRI's message of "Mon, 16 Sep 2002 17:54:18 -0400") Message-ID: <87hegpbne4.fsf@cenderis.demon.co.uk> User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hall Jeffrey S NPRI writes: > Actually, I figured out my problem. I got burned by the zsh not > splitting parameter substitutions into multiple words. [...] > This "feature" of zsh should be better known. I've used the zsh for > like 8 years and never stumbled (staggered) across this problem > before. It's in the FAQ. It's a feature if you want to treat strings consistently whether or not they happen to contain spaces.