Re: [Bashburn-info] Substantial change to the configure function.

[Nick W. <ni...@uk...>]

On Wed, 3 Sep 2008 10:04:34 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:
 
> =>
> =>OK, I get syntax errors when starting... it looks like bash doesn't
> =>like empty functions.  If I remove them, all seems well but I don't
> =>know what you was doing here so haven't changed anything.
> =>
> =>line 285: syntax error near unexpected token `}'
> =>
> =>source_language_modules()
> =>{
> =>}   <---------------------------------
> 
> This goes to show that committing at 01:30 is risky business.
> 
> 
> BTW, bash is correct. A function is not allowed to be empty. There
> must be something there. The standard null statement is:
> 
> :
> 
> continue or break have no meaning outside of the context of a loop.
> 
> But you did identify another minor problem in configure.sh. Please 
> update.

Steve,

Still doesn't save any changes to configuration.  It shows the changed
value* perfectly (good idea!), but applying changes doesn't save.

Nick
-- 
Free Software Foundation Associate Member 5508