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

[Steven W. O. <st...@sy...>]

On Wednesday, Sep 3rd 2008 at 17:04 -0000, quoth Nick Warne:


=>OK, I am at my wits end.  I have tried everything.  I totally removed
=>everything *bashburn* from my system.

This is good. I've only lost half of my wits. ;-)

=>I re-installed.
=>
=>Same issue - config changes do not get saved.
=>
=>I totally removed everything *bashburn* from my system, trashed my
=>local SVN and re-checked out.
=>
=>Same issue - config changes do not get saved.
=>
=>I totally removed everything *bashburn* from my system.  I unhashed
=>bash (hash -r). I re-installed using default install (I use the
=>Slackware option).
=>
=>Same issue - config changes do not get saved.
=>
=>I dunno what else to try, really I don't.
=>
=>I guess next step is for me to revert to an early version and find
=>what/when broke for me...

You're right. It does sound desperate. Let's do this.

Mod your local copy of apply_options.sh and in the function conf_set_aval, 
put a set -x set +x around the while read loop. It should look like this:

    set -x
    while read line
    do
	IFS=:
	<stuff>
    done < $BBCONFFILE > $tmpfile
    set +x

Start script and from there run bb.

Go into configure and change one thing.

Then apply.

Exit bb.

Exit script.

By looking at the trace, you should see:
the value of size should be 1.
The value of desc[0] should be "theVarYouChanged:newval"

Send me the typescript file.

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net