From owner-freebsd-questions@FreeBSD.ORG Sat Mar 21 19:19:12 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9C3D106566B for ; Sat, 21 Mar 2009 19:19:12 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id ADF0C8FC21 for ; Sat, 21 Mar 2009 19:19:12 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 6863 invoked from network); 21 Mar 2009 19:19:12 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 21 Mar 2009 19:19:12 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 3154E50824; Sat, 21 Mar 2009 15:19:06 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id A4AC91D31D; Sat, 21 Mar 2009 15:19:05 -0400 (EDT) To: Chuck Robey References: <20090321124859.GA27682@anton.digitaltorque.ca> <20090321142122.GA99623@torus.slightlystrange.org> <44tz5m7sau.fsf@lowell-desk.lan> <49C532E6.3080903@telenix.org> From: Lowell Gilbert Date: Sat, 21 Mar 2009 15:19:05 -0400 In-Reply-To: <49C532E6.3080903@telenix.org> (Chuck Robey's message of "Sat\, 21 Mar 2009 14\:33\:10 -0400") Message-ID: <44k56iptue.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Lowell Gilbert , freebsd-questions@freebsd.org Subject: Re: bash suddenly doesn't like $() syntax X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Mar 2009 19:19:13 -0000 Chuck Robey writes: > I've had stuff like this happen to me, once in a while. it's NEVER a fact of > bash really suddenly losing something so major. What you have to is to look at > previous parts of your code, for things like unclosed parens, unclosed quotes, > things like that. The errors aren't overly helpful, but if you look at previous > lines, you'll find it there, believe me. That happens, but was not the case in this instance. A particular syntax really did break in bash if you compiled it with our system yacc(1). I don't know whether the problem was in yacc or in the bash build assuming Gnuisms from bison, but bash really was broken for a while on $(...) formulations. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/