From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28380 invoked from network); 5 Aug 1999 14:22:22 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Aug 1999 14:22:22 -0000 Received: (qmail 20472 invoked by alias); 5 Aug 1999 14:22:13 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7379 Received: (qmail 20465 invoked from network); 5 Aug 1999 14:22:13 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "Peter Stephenson" , Subject: RE: PATCH: parameter and quoting (was: Re: Completion problems.) Date: Thu, 5 Aug 1999 18:22:09 +0400 Message-ID: <002c01bedf4d$e7442030$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" 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) In-Reply-To: <9908051318.AA19836@ibmth.df.unipi.it> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 > > The first possibility sounds sensible to me, too, since ksh allows > you to do > > a="'" > echo "${a%'}" > > although bash complains as well. It's probably a grey area, since the > single UNIX specification says > Unfortunately, Single UNIX requires, that quotes be matched. This is from the description of double-quotes: == Within the string of characters from an enclosed ${ to the matching "}", an even number of unescaped double-quotes or single-quotes, if any, must occur. == It means, that preceding example MUST be echo "${a%\'}" /andrej