On Fri, 13 Mar 2009 13:16:07 -0600
Tim Judd wrote:
>On Thu, Mar 12, 2009 at 11:35 PM, bf wrote:
>I'm wondering if a fix can be accomplished due to a semicolon within
>the ()s to complete a command line. Similar to how find(1) expression
>works, you have to end the expression with a semicolon i
On Thu, Mar 12, 2009 at 11:35 PM, bf wrote:
>
>
> > > {Problem with Bash-4 and $(command) ...}:
> > [...]
> > > I found the same problem, and have reverted to
> > > bash3.2 until it's sorted out.
> >
> > See if the following helps.
> >
> > http://tiswww.case.edu/php/chet/bash/COMPAT
> >
> > Espe
> > {Problem with Bash-4 and $(command) ...}:
> [...]
> > I found the same problem, and have reverted to
> > bash3.2 until it's sorted out.
>
> See if the following helps.
>
> http://tiswww.case.edu/php/chet/bash/COMPAT
>
> Especially:
>
> 38. Since bash-4.0 now follows Posix rules for finding
On 13.03.2009 02:04, Mark McConnell wrote:
> On 12 Mar 2009 at 10:25, Jerry wrote:
> {Problem with Bash-4 and $(command) ...}:
[...]
> I found the same problem, and have reverted to
> bash3.2 until it's sorted out.
See if the following helps.
http://tiswww.case.edu/php/chet/bash/COMPAT
Especia
On 12 Mar 2009 at 10:25, Jerry wrote:
{Problem with Bash-4 and $(command) ...}:
>
> Is this a known problem with Bash-4? I have not been
> able to find anything about it on the Bash site.
>
> Jerry
> ges...@yahoo.com
>
I found the same problem, and have reverted to
bash3.2 until it's sorted
