Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Mar 2009 14:33:10 -0400
From:      Chuck Robey <>
To:        Lowell Gilbert <>
Subject:   Re: bash suddenly doesn't like $() syntax
Message-ID:  <>
In-Reply-To: <44tz5m7sau.fsf@lowell-desk.lan>
References:  <>	<> <44tz5m7sau.fsf@lowell-desk.lan>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Hash: SHA1

Lowell Gilbert wrote:
> "Daniel Bye" <> writes:
>> On Sat, Mar 21, 2009 at 08:49:01AM -0400, Michael P. Soulier wrote:
>>> Hello,
>>> I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. All
>>> of a sudden when I login, my standard .profile and .bashrc are causing a bunch
>>> of error messages, like so
>>> -bash: command substitution: line 39: syntax error near unexpected token `)'
>>> -bash: command substitution: line 39: `    }")'
>>> It would see that bash no longer likes the $() command substitution syntax.
>>> Does that mean that it's defaulting to some sort of posix compatibility mode
>>> now? 
>> It's a bug in bash 4. It was discussed here a few days ago. I would
>> deinstall v.4 and install shells/bash3 until the bug's fixed.
> Which happened a week ago.

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.
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla -


Want to link to this message? Use this URL: <>