From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22217 invoked from network); 16 Apr 1999 09:27:49 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 16 Apr 1999 09:27:49 -0000 Received: (qmail 3224 invoked by alias); 16 Apr 1999 09:27:41 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6052 Received: (qmail 3213 invoked from network); 16 Apr 1999 09:27:40 -0000 From: "Andrej Borsenkow" To: "Bart Schaefer" , Subject: RE: BUG: zsh-3.1.5-pws-14: parameter expansion not working properly Date: Fri, 16 Apr 1999 13:26:57 +0400 Message-ID: <000201be87eb$46295210$21c9ca95@mowp.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <990416020418.ZM13627@candle.brasslantern.com> > > All that aside, a desirable (?) effect of the current interpretation is > that join reverses split (except for the initial array-to-scalar change): > ... as long as no SH_WORD_SPLIT is in effect. IFS splits may remove more than IFS joins add. > zsh% print -l ${(j/:/)${(s/:/)foo}} > a:b x:y > > With your interpretation, this would yield a:b:x:y. Don't laugh - it was exactly what I needed once. And I personally find nothing wrong or illogical with it. /andrej