From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6972 invoked from network); 28 Jun 2004 17:27:02 -0000 Received: from odin.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.85) by ns1.primenet.com.au with SMTP; 28 Jun 2004 17:27:02 -0000 Received: (qmail 7529 invoked from network); 28 Jun 2004 18:36:57 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 28 Jun 2004 18:36:57 -0000 Received: (qmail 7217 invoked by alias); 28 Jun 2004 17:26:45 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20116 Received: (qmail 7206 invoked from network); 28 Jun 2004 17:26:44 -0000 Received: from odin.dotsrc.org (HELO a.mx.sunsite.dk) (qmailr@130.225.247.85) by sunsite.dk with SMTP; 28 Jun 2004 17:26:44 -0000 Received: (qmail 7272 invoked from network); 28 Jun 2004 18:36:49 -0000 Received: from unknown (HELO moonbase.zanshin.com) (@167.160.213.139) by a.mx.sunsite.dk with SMTP; 28 Jun 2004 18:36:38 -0000 Received: from toltec.zanshin.com (toltec.zanshin.com [64.84.47.166]) by moonbase.zanshin.com (8.12.11/8.12.11) with ESMTP id i5SHQVdr028591; Mon, 28 Jun 2004 10:26:31 -0700 Date: Mon, 28 Jun 2004 10:26:31 -0700 (PDT) From: Bart Schaefer Reply-To: zsh-workers@sunsite.dk To: zsh-workers@sunsite.dk cc: 255788-forwarded@bugs.debian.org Subject: Re: PATCH: (2): Bug#255788: $'' does not work after <<< In-Reply-To: <200406281529.i5SFTLWU003104@news01.csr.com> Message-ID: References: <200406281529.i5SFTLWU003104@news01.csr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63 X-Spam-Hits: 0.0 On Mon, 28 Jun 2004, Peter Stephenson wrote: > Grud. I can easily fix this. I will then commit it without asking, in > case there are yet more problems... Well, only kinda. See what happens with unbalanced backticks: schaefer<501> cat <<`echo `foo `bar bquote> ` bquote> ` bquote> ` bquote> The only way to get out of this is to interrupt the shell. However, bash appears to have exactly this same problem, though it's harder to tell where the parser is stuck because bash lacks the %_ expando.