From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16683 invoked from network); 6 Jul 2000 10:19:47 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Jul 2000 10:19:47 -0000 Received: (qmail 22615 invoked by alias); 6 Jul 2000 10:19:27 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 3258 Received: (qmail 22608 invoked from network); 6 Jul 2000 10:19:27 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "Peter Stephenson" , "Zsh users list" Subject: RE: Probs with nested braces in PROMPT Date: Thu, 6 Jul 2000 14:19:24 +0400 Message-ID: <000801bfe733$a8aef590$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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: <0FX900MG0TOBBR@la-la.cambridgesiliconradio.com> > > The problem was that ordinary ${...} doesn't know about > %-substitution in > prompts, nor should it (that would be a horrendous > complication involving > different levels of substitution). So it took the brace in > `%}' as the > brace closing the substitution. Yes, of course. But why it did it only when parameter was undefined? I mean, parsing is done by lexer - and it has to find the closing brace in any case and lexer does not know (is it true?) about parameter values. That is incosistent IMHO and smells more like a bug. -andrej