delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/07/07/23:50:29

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <ba40711f050707205050f15f3e@mail.gmail.com>
Date: Thu, 7 Jul 2005 23:50:18 -0400
From: Lev Bishop <lev DOT bishop AT gmail DOT com>
Reply-To: Lev Bishop <lev DOT bishop AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Broken parse on `'${'`
In-Reply-To: <42CDE346.30908@byu.net>
Mime-Version: 1.0
References: <42CDE346 DOT 30908 AT byu DOT net>
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j683oQ6k025996

On 07/07/05, Eric Blake wrote:

> zsh$ bash
> bash$ echo `echo '${'`
> >
> # Hmm - I was just incorrectly presented PS2, asking to try to continue
> what bash thought was an incomplete ${ variable substitution

Actually, this is a bad example, because even if bash did parse
correctly, there would be still an incomplete ${ substitution for the
outer echo

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019