bashburn-info — BashBurn mailing list

Re: [Bashburn-info] Problems in menues of config

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

On Monday, Sep 8th 2008 at 09:49 -0000, quoth Nick Warne:

=>On Sun, 7 Sep 2008 21:42:19 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>
=>> I think we're slowly getting this bad boy whipped into shape. It's
=>> looking more like bash code every day.
=>> 
=>
=>Two more 'issues'.
=>
=>The main menu sometimes prints garbage.  To replicate:
=>
=>Start BB
=>
=>go to configuration menu (5).
=>
=>Change something (do not APPLY).
=>
=>Change something else (do not APPLY).
=>
=>You now have two values marked ()*
=>
=>Revert changes - exit configuration menu.
=>
=>The main menu item 0 now has garbage from the last reverted $VAR
=>
=>Also, if 'revert' is used, and you do then exit the menu, BB still
=>has the 'BB_CONFIG_MODIFIED' flag set when it shouldn't, so you
=>still have to go through the 'really sure' dialogue.  This should only
=>happen if a change is made and 'revert' is NOT used before exiting.

I'm at 528 and I'm not seeing the problem. :-( 

The menu printing garbage problem was something I never specifically 
fixed, but when I went to the new bbmenu, the problem went away.

The second problem with BB_CONFIG_MODIFIED not being properly set was 
fixed.

Can you check where you're at?

-- 
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

Re: [Bashburn-info] bbmenu is now modified

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

On Wed, 10 Sep 2008 10:40:14 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Wednesday, Sep 10th 2008 at 02:54 -0000, quoth Nick Warne:
> 
> =>On Tue, 9 Sep 2008 19:39:43 -0400 (EDT)
> =>"Steven W. Orr" <st...@sy...> wrote:
> =>
> =>> to operate the same way as bbconfmenu. Nick, I don't know what the
> =>> problem was that you had previously described. I saw it so I  know
> =>> you're not hallucinating, but when I made the change to bbmenu,
> the =>> problem seemed to have been eliminated.
> =>> 
> =>> PLEASE let me know if you find any problems.
> =>
> =>Indeed, the earlier issue now seems fixed;  The advanced menu with
> no =>help text is still apparent, though.  But...
> 
> I have just one word: Oops. It's fixed. :-)
> 
> =>In advanced menu, if you change something, 'revert changes' doesn't
> =>work, and IF you use 'revert changes', 'apply defaults' then
> =>doesn't work either.  NOT using 'revert changes', all other options
> =>appear to work fine, though.  I haven't tested this on the main
> menu.
> 
> Also fixed. Thanks.

OK, now this works, we are back to the garbage in the main menu after
changing and reverting two values.

> =>Also a cosmetic change.  Why have 'Configure BashBurn' and Advanced
> =>bashBurn config.'?
> =>
> =>We know it is BashBurn... surely just 'Configuration' and Advanced
> =>Configuartion' is required here?
> 
> Sure.

I just meant:

5) Configuration
6) Advanced Configuration

> 
> As the changes to bb start to wind down, there are new text strings 
> creeping in and old ones that might want to change. They should be
> handled in less of an ad hoc manner; If I change a string now, I'm
> afraid it'll just leave the other languages out of sync.
> 
> Which brings up a new topic... The way that we're handling the
> different language problems right now works but it feels somewhat
> unwieldy. We have strings in lang/English/somefile.lang and then we
> have copies of the file in lang/!English/somefile.lang . Some of the
> files are mostly translated. (Good job BTW.) Some languages are there
> in good shape, but if a string changes, I don't see a system for
> *knowing* that the other languages have to be followed up. Also, we
> have a lot of strings that are duplicated, and changing one instance
> begs the questions whether followup can be managed.
> 
> So here's the $64 question: Does anyone here have any experience with 
> gettext/msgfmt/po files/pot files/ etc? Should we keep going the way
> we are? I ask this with no prior experience using pot files.


Ummm.  I have never dealt  with po files (being English, I never had
the cause to, really), but am aware of them and the general way they
work. Good time to learn, I guess :-)

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Gettext support

[Anders L. <and...@gm...>]

My reply to Steven was sent only to him. I'm reposting the message here.

> As the changes to bb start to wind down, there are new text strings 
> creeping in and old ones that might want to change. They should be
handled 
> in less of an ad hoc manner; If I change a string now, I'm afraid
it'll 
> just leave the other languages out of sync.
> 
> Which brings up a new topic... The way that we're handling the
different 
> language problems right now works but it feels somewhat unwieldy. We
have 
> strings in lang/English/somefile.lang and then we have copies of the
file 
> in lang/!English/somefile.lang . Some of the files are mostly
translated. 
> (Good job BTW.) Some languages are there in good shape, but if a
string 
> changes, I don't see a system for *knowing* that the other languages
have 
> to be followed up. Also, we have a lot of strings that are duplicated,
and 
> changing one instance begs the questions whether followup can be
managed.
> 
> So here's the $64 question: Does anyone here have any experience with 
> gettext/msgfmt/po files/pot files/ etc? Should we keep going the way
we 
> are? I ask this with no prior experience using pot files.
> 


All experience with po files I have is that I helped translate an
application to Swedish a bunch of years ago. I have no experience in
actually adding support for it though.

I agree with you though Steven. The translation system is sort of a
mess. It works yes but it's kind of awkward to work with (All credit to
me I suppose). I think it would be a good idea to look into using
gettext. I'm sure it would make translators lives a lot easier. 

-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] bbmenu is now modified

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

On Wednesday, Sep 10th 2008 at 02:54 -0000, quoth Nick Warne:

=>On Tue, 9 Sep 2008 19:39:43 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> to operate the same way as bbconfmenu. Nick, I don't know what the
=>> problem was that you had previously described. I saw it so I  know
=>> you're not hallucinating, but when I made the change to bbmenu, the
=>> problem seemed to have been eliminated.
=>> 
=>> PLEASE let me know if you find any problems.
=>
=>Indeed, the earlier issue now seems fixed;  The advanced menu with no
=>help text is still apparent, though.  But...

I have just one word: Oops. It's fixed. :-)

=>In advanced menu, if you change something, 'revert changes' doesn't
=>work, and IF you use 'revert changes', 'apply defaults' then
=>doesn't work either.  NOT using 'revert changes', all other options
=>appear to work fine, though.  I haven't tested this on the main menu.

Also fixed. Thanks.

=>Also a cosmetic change.  Why have 'Configure BashBurn' and Advanced
=>bashBurn config.'?
=>
=>We know it is BashBurn... surely just 'Configuration' and Advanced
=>Configuartion' is required here?

Sure. 

As the changes to bb start to wind down, there are new text strings 
creeping in and old ones that might want to change. They should be handled 
in less of an ad hoc manner; If I change a string now, I'm afraid it'll 
just leave the other languages out of sync.

Which brings up a new topic... The way that we're handling the different 
language problems right now works but it feels somewhat unwieldy. We have 
strings in lang/English/somefile.lang and then we have copies of the file 
in lang/!English/somefile.lang . Some of the files are mostly translated. 
(Good job BTW.) Some languages are there in good shape, but if a string 
changes, I don't see a system for *knowing* that the other languages have 
to be followed up. Also, we have a lot of strings that are duplicated, and 
changing one instance begs the questions whether followup can be managed.

So here's the $64 question: Does anyone here have any experience with 
gettext/msgfmt/po files/pot files/ etc? Should we keep going the way we 
are? I ask this with no prior experience using pot files.

-- 
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

Re: [Bashburn-info] bbmenu is now modified

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

On Tue, 9 Sep 2008 19:39:43 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> to operate the same way as bbconfmenu. Nick, I don't know what the
> problem was that you had previously described. I saw it so I  know
> you're not hallucinating, but when I made the change to bbmenu, the
> problem seemed to have been eliminated.
> 
> PLEASE let me know if you find any problems.

Indeed, the earlier issue now seems fixed;  The advanced menu with no
help text is still apparent, though.  But...

In advanced menu, if you change something, 'revert changes' doesn't
work, and IF you use 'revert changes', 'apply defaults' then
doesn't work either.  NOT using 'revert changes', all other options
appear to work fine, though.  I haven't tested this on the main menu.

Also a cosmetic change.  Why have 'Configure BashBurn' and Advanced
bashBurn config.'?

We know it is BashBurn... surely just 'Configuration' and Advanced
Configuartion' is required here?

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] bbmenu is now modified

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

to operate the same way as bbconfmenu. Nick, I don't know what the problem 
was that you had previously described. I saw it so I  know you're not 
hallucinating, but when I made the change to bbmenu, the problem seemed to 
have been eliminated.

PLEASE let me know if you find any problems.

Marcus: At the bottom of BashBurn.sh is a variable assignment:

bb_main_menu=MAIN

We need to add that to the lang files. It is now no longer legal to pass a 
string value as the title arg to bbmenu. It must now be the name of a 
variable.

One interesting construct was in dealing with a changing value for BBLANG. 
The apply function for configure (config_apply) calls set_descriptors, 
which is a nested function inside bbmenu. But config_apply can't reset the 
values for its caller which is where the main menu originates. So instead 
of BashBurn calling bbmenu for the main menu, I caused the action for the 
invocation of the configure menu to make a return. [BTW, I'm painfully 
aware that what I'm writing is probably not intelligble. More docs will be 
needed.] Anyways, the main menu now has to be called in an infinite loop 
so that the main menu will reinitialize the evaluation of the main menu.

-- 
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

Re: [Bashburn-info] Problems in menues of config

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

On Monday, Sep 8th 2008 at 09:49 -0000, quoth Nick Warne:

=>Two more 'issues'.
=>
=>The main menu sometimes prints garbage.  To replicate:
=>
=>Start BB
=>
=>go to configuration menu (5).
=>
=>Change something (do not APPLY).
=>
=>Change something else (do not APPLY).
=>
=>You now have two values marked ()*
=>
=>Revert changes - exit configuration menu.
=>
=>The main menu item 0 now has garbage from the last reverted $VAR
=>
=>Also, if 'revert' is used, and you do then exit the menu, BB still
=>has the 'BB_CONFIG_MODIFIED' flag set when it shouldn't, so you
=>still have to go through the 'really sure' dialogue.  This should only
=>happen if a change is made and 'revert' is NOT used before exiting.

As described earlier, I changed bbconfmenu around so that we are now 
passing in the name of the array instead of the array values. It works and 
it solves that particular problem. Here's what's still left:

* Nick, the problem you described above where you revert and then try to 
go Back is now fixed, but the problem with funny characters in the Main 
menu are still appearing. Manyana.

* Also, this whole changing BBLANG thing is a bigger schmageggy than you 
might think. The way this is going to have to work is that I'm going to 
have to create a new global variable which will be a stack of variable 
names. The general solution won't buy us anything so maybe a simple list 
is all we really need. But the point is that there's more to this. The 
converversion I did tonight will also have to be done to bbmenu the same 
as it was done to bbconfmenu, and for the same reason.

Is this making sense? I could get hit by a bus and I sort of hope that 
someone is picking this stuff up.

Also, Markus, small syntax problem in lang/German/configure.lang. Please 
make sure you update.

Bedtime.

-- 
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

[Bashburn-info] Addressing the problem of changing the language in midstream.

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

(Rambling on for myself as well as others...)

Markus came up with an interesting bug which I have been mulling over for 
a while now. The problem is this. We cave a call stack that looks like 
this

BashBurn
   bbmenu(MAIN)
     configure
       bbconfmenu(Configure)

What gets passed to bbmenu is "${mainmenu[@]}". Inside bbmenu, we call 
configure which then calls bbconfmenu whose args are "${conf_menuitems[@]}".

After we change BBLANG, the value of mainmenu and conf_menuitems is 
properly modified, but the user won't see the changes after the variables 
are modified because the args to bbconfmenu and bbmenu were not changed.

I did some quick experimenting on how to solve the problem and I think I 
have a solution:

Below is a small script to test how to not pass all of the elements of the 
array and to instead pass the name. The problem is that we can't lose the 
ability to access the elements of the array even though they might contain 
whitespace. There's more to this because some of the elements of the array 
will be containing code that in turn also needs to be eval'd again. 
Somehow it all seems to work. :-)

#! /bin/bash
aa1="Hello there"
aa2="Goodbye all@ls -l /tmp"
aa3="Thank you"

gg1="Guten Tag"
gg2='Auf Wiedersehen@ls -l /tmp'
gg3='Danke'

typeset -a ar=( "$aa1" "$aa2" "$aa3" )

foo()
{
     typeset -a i_ar
     echo "$@"
     i_ar=( $(eval "echo \"$@\"") )
     echo "i_ar[@]=${i_ar[@]}"
     echo "i_ar[2]=${i_ar[2]}"
     echo 'setting ar to gg'
     ar=( "$gg1" "$gg2" "$gg3" )
     i_ar=( $(eval "echo \"$@\"") )
     echo "i_ar[@]=${i_ar[@]}"
     echo "i_ar[2]=${i_ar[2]}"
     echo $(eval "echo \"$@\"")
}

foo '"${ar[@]}"'
echo 'foo failed'

foo2()
{
     typeset aa="${1}"
     typeset -a bb
     echo "aa=$aa"
     bb=( $(eval "echo \"\${$aa[@]}\"" ) )
     echo "bb:${bb[@]}"
     echo "bb[2]:${bb[2]}"
}

foo2 ar
echo 'foo2 fails.'

foo3()
{
     typeset old_IFS="$IFS"
     typeset IFS="$old_IFS"
     typeset aa="${1}"
     typeset -a bb
     typeset -i ii
     echo "aa=$aa"
     bbsize=$(eval "echo \"\${#$aa[@]}\"" )
     echo "bbsize=$bbsize"
     for (( ii=0; ii<bbsize; ii++ ))
     do
 	bb[ii]=$(eval "echo \"\${$aa[ii]}\"" )
     done
     echo "bb:${bb[@]}"
     echo "bb[0]:${bb[0]}"
     echo "bb[1]:${bb[1]}"
     echo "bb[2]:${bb[2]}"
     ar=( "$gg1" "$gg2" "$gg3" )
     bbsize=$(eval "echo \"\${#$aa[@]}\"" )
     for (( ii=0; ii<bbsize; ii++ ))
     do
 	bb[ii]=$(eval "echo \"\${$aa[ii]}\"" )
     done
     echo "bb:${bb[@]}"
     echo "bb[0]:${bb[0]}"
     echo "bb[1]:${bb[1]}"
     echo "bb[2]:${bb[2]}"
     IFS=@
     set -- ${bb[1]}
     echo "1:$1"
     echo "2:$2"
     eval $2
}

foo3 ar
echo 'This succeeds.'

-- 
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

Re: [Bashburn-info] Problems in menues of config

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

On Monday, Sep 8th 2008 at 09:49 -0000, quoth Nick Warne:

=>On Sun, 7 Sep 2008 21:42:19 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>
=>> I think we're slowly getting this bad boy whipped into shape. It's
=>> looking more like bash code every day.
=>> 
=>
=>Two more 'issues'.
=>
=>The main menu sometimes prints garbage.  To replicate:
=>
=>Start BB
=>
=>go to configuration menu (5).
=>
=>Change something (do not APPLY).
=>
=>Change something else (do not APPLY).
=>
=>You now have two values marked ()*
=>
=>Revert changes - exit configuration menu.
=>
=>The main menu item 0 now has garbage from the last reverted $VAR
=>
=>Also, if 'revert' is used, and you do then exit the menu, BB still
=>has the 'BB_CONFIG_MODIFIED' flag set when it shouldn't, so you
=>still have to go through the 'really sure' dialogue.  This should only
=>happen if a change is made and 'revert' is NOT used before exiting.

I see it. Thanks.

Also, I think I have a fix in mind for the language problem that Markus 
saw yesterday. That one is tricky because the data that is being displayed 
is still on the stack.

I'll play more tonight.

-- 
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

Re: [Bashburn-info] Problems in menues of config

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

On Sun, 7 Sep 2008 21:42:19 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:


> I think we're slowly getting this bad boy whipped into shape. It's
> looking more like bash code every day.
> 

Two more 'issues'.

The main menu sometimes prints garbage.  To replicate:

Start BB

go to configuration menu (5).

Change something (do not APPLY).

Change something else (do not APPLY).

You now have two values marked ()*

Revert changes - exit configuration menu.

The main menu item 0 now has garbage from the last reverted $VAR

Also, if 'revert' is used, and you do then exit the menu, BB still
has the 'BB_CONFIG_MODIFIED' flag set when it shouldn't, so you
still have to go through the 'really sure' dialogue.  This should only
happen if a change is made and 'revert' is NOT used before exiting.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Problems in menues of config

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

On Sunday, Sep 7th 2008 at 18:58 -0000, quoth Markus Kollmar:

=>I actualized the german translation.
=>Doing this I recognized that in the configure menues are some bugs:
=>
=>- the language does not change to actual selected language (tested with 
=>german translation, which now should be actual) in the config         
=>sub-menues,  instead it is still english translation.
=>
=>- for some items like option '19' (gaps config) there appears no 
=>description in configure sub-menue.
=>
=>- the headers at top of for the config menue columns don't appear, which 
=>should probably be:
=>     bb_conf_menu_toptext1=Setup
=>     bb_conf_menu_toptext2='Current value'

Hi Markus. Thanks for spotting the problems.

* I changed the delimiter for menu descriptors from : to @. That seems to 
fix the problem. (only because @ is not in use.) :-(

* Also, there was an eval problem in bbmenu. I think we should be ok now.

* And I added back the missing header line in the config menus.

I think we're slowly getting this bad boy whipped into shape. It's looking 
more like bash code every day.

-- 
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

Re: [Bashburn-info] Problems in menues of config

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

On Sunday, Sep 7th 2008 at 18:58 -0000, quoth Markus Kollmar:

=>I actualized the german translation.
=>Doing this I recognized that in the configure menues are some bugs:
=>
=>- the language does not change to actual selected language (tested with 
=>german translation, which now should be actual) in the config         
=>sub-menues,  instead it is still english translation.
=>
=>- for some items like option '19' (gaps config) there appears no 
=>description in configure sub-menue.
=>
=>- the headers at top of for the config menue columns don't appear, which 
=>should probably be:
=>     bb_conf_menu_toptext1=Setup
=>     bb_conf_menu_toptext2='Current value'

Got it. Looks like the use of a colon is the problem. I'll switch the 
stuff around so that the new universal delimiter will henceforth be The 
Dreaded Ampersand. This means that people will not longer be allowed to 
use That Auspicious Character in any descriptive text.

-- 
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

[Bashburn-info] Problems in menues of config

[Markus K. <mar...@on...>]

I actualized the german translation.
Doing this I recognized that in the configure menues are some bugs:

- the language does not change to actual selected language (tested with 
german translation, which now should be actual) in the config         
sub-menues,  instead it is still english translation.

- for some items like option '19' (gaps config) there appears no 
description in configure sub-menue.

- the headers at top of for the config menue columns don't appear, which 
should probably be:
     bb_conf_menu_toptext1=Setup
     bb_conf_menu_toptext2='Current value'


Markus Kollmar

[Bashburn-info] check_cd_status and ask_for_blanking are wrong

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

I don't know for sure, but I suspect that this is functionality that got 
lorst when we converted to a model with only one process.

We only call ask_for_blanking if check_for_cdstatus says that the cd is 
USED. Then ask_for_blanking only returns with not status check. I think 
that its return statement was menat to be an exit. I'm changing it so that 
it will return success or failure. Then that has to be checked as well.

-- 
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

Re: [Bashburn-info] Yet more changes to ...

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

On Sunday, Sep 7th 2008 at 10:30 -0000, quoth Steven W. Orr:

=>On Sunday, Sep 7th 2008 at 03:10 -0000, quoth Nick Warne:
=>
=>=>If you go into an option in the advanced config, none of the help text
=>=>is/are displayed.
=>
=>I'm getting confused. I go into the Advanced menu and select
=>
=>7 CD Copying Options
=>
=>You're right that there is no info displayed, but there is so info that 
=>was prepared. If someone wants to write it we can add it.
=>
=>What I can do is to eliminate the info bars if there is no info to write.
=>
=>Is there more than I'm not getting?
=>

Ok, here's the new deal. It's good to be able to hit return and mean 
"Excuse me, I didn't mean to hit this." But we also need a way to set 
something to a null value. So The New Deal goes like this:

* Hit return (empty text) and that gets you out without making a change.
* Supply the escape string "" (i.e., two double quotes) and bb knows you 
want to set to the null string.

-- 
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

Re: [Bashburn-info] Yet more changes to ...

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

On Sunday, Sep 7th 2008 at 03:10 -0000, quoth Nick Warne:

=>If you go into an option in the advanced config, none of the help text
=>is/are displayed.

I'm getting confused. I go into the Advanced menu and select

7 CD Copying Options

You're right that there is no info displayed, but there is so info that 
was prepared. If someone wants to write it we can add it.

What I can do is to eliminate the info bars if there is no info to write.

Is there more than I'm not getting?

-- 
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

Re: [Bashburn-info] Yet more changes to ...

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

On Sunday, Sep 7th 2008 at 03:10 -0000, quoth Nick Warne:

=>On Sun, 7 Sep 2008 00:42:38 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> I decided that it wasn't worth it to make all the menus common. So
=>> the new setup is that the bbmenu file now contains two menu types:
=>> bbmenu for all the menus except configuration, and now there's
=>> bbmenuconf for the configuration and the advanced configuration. One
=>> trade-off was required. (Please don't make me have to fix it): The
=>> Advanced menus is now in the Main menu and no longer in the
=>> Configuration menu. Like I said about he bbmenu function, that
=>> there's some serious eval/quoting/syntax games going on. Whatever I
=>> said about bbmenu is about an order of magnitude more (ahem)
=>> interesting in bbmenuconf.
=>
=>Two same things:
=>
=>If you go into an option in either of the config menus, and just press
=>[ENTER] to exit without changing it, the value gets set to NULL i.e. ()*

This is a (relatively) new feature. I changed this so that you had the 
ability to be able to set a value to null. Prior to this, I set a variable 
to null and then found I couldn't set it back.

=>If you go into an option in the advanced config, none of the help text
=>is/are displayed.

You're right. I'll look at at it.

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steven W. Orr

Re: [Bashburn-info] Yet more changes to ...

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

On Sun, 7 Sep 2008 00:42:38 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> I decided that it wasn't worth it to make all the menus common. So
> the new setup is that the bbmenu file now contains two menu types:
> bbmenu for all the menus except configuration, and now there's
> bbmenuconf for the configuration and the advanced configuration. One
> trade-off was required. (Please don't make me have to fix it): The
> Advanced menus is now in the Main menu and no longer in the
> Configuration menu. Like I said about he bbmenu function, that
> there's some serious eval/quoting/syntax games going on. Whatever I
> said about bbmenu is about an order of magnitude more (ahem)
> interesting in bbmenuconf.

Two same things:

If you go into an option in either of the config menus, and just press
[ENTER] to exit without changing it, the value gets set to NULL i.e. ()*

If you go into an option in the advanced config, none of the help text
is/are displayed.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Yet more changes to ...

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

I decided that it wasn't worth it to make all the menus common. So the 
new setup is that the bbmenu file now contains two menu types: bbmenu for 
all the menus except configuration, and now there's bbmenuconf for the 
configuration and the advanced configuration. One trade-off was required. 
(Please don't make me have to fix it): The Advanced menus is now in the 
Main menu and no longer in the Configuration menu. Like I said about he 
bbmenu function, that there's some serious eval/quoting/syntax games going 
on. Whatever I said about bbmenu is about an order of magnitude more 
(ahem) interesting in bbmenuconf.

All this stuff is currently inadequately documented. I'll try and tickle 
some more betterer comments in ahead.

Also, I decided that the edit, install, run cycle was getting four 
keystrokes more tedious than it needed to be so (at least for now) I added 
a -y option to Install.sh which will make it think you said yes to the 
question that it no longer has to ask you.

All questions are more than welcome, but for now it's bedtime, we're in 
the middle of a hurricane, and I still have to let the dogs out before I 
can knock off for the night.

Donatella Nabatti

-- 
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

Re: [Bashburn-info] Functionality TESTING thread

[Anders L. <and...@gm...>]

On Sun, 2008-08-31 at 17:02 +0100, Nick Warne wrote:
> I think we ought to start a thread reporting successful functionality
> 
> I just fixed a broken data recording - committed.
> 
> So please just reply to this thread as each function is proven to work
> so we have some sort of visible guide.
> 
> 
> Data recording WORKS
> 

Just reporting I've burnt a data cd as well as an iso, both works fine.

-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] Functionality TESTING thread

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

On Sun, 31 Aug 2008 17:37:09 +0100
Nick Warne <ni...@uk...> wrote:

> On Sun, 31 Aug 2008 17:02:19 +0100
> Nick Warne <ni...@uk...> wrote:
> 
> > I think we ought to start a thread reporting successful
> > functionality
> > 
> > I just fixed a broken data recording - committed.
> > 
> > So please just reply to this thread as each function is proven to
> > work so we have some sort of visible guide.
> > 
> > 
> > Data recording WORKS
> > 
> 
> Burning ISO works
> 

OK, update.  I just burnt a *.ogv file to CD(data recording).

All works perfectly.

BTW, worth a watch:

http://www.gnu.org/fry/happy-birthday-to-gnu.html

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Multiple problems in burning.sh

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

On Fri, 5 Sep 2008 21:54:05 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Friday, Sep 5th 2008 at 16:20 -0000, quoth Nick Warne:
> 
> =>On Fri, 5 Sep 2008 14:20:49 -0400 (EDT)
> =>"Steven W. Orr" <st...@sy...> wrote:
> =>
> =>
> =>> =>Trouble is here, Steve is how to test it.  I don't have any
> stuff to =>> =>burn/discs to test with?
> =>> =>
> =>> =>How can we test it all?
> =>> =>
> =>> =>Is there a switch in cdrecord & friends that goes through the
> =>> motions =>(like --dry-run) and just pretends to burn something?
> =>> 
> =>> I see a -dummy option on cdrecord:
> =>> 
> =>>    -dummy The CD/DVD-Recorder will go through all steps of the
> =>> recording process,  but the laser is turned off during this
> =>> procedure. It is recommended to run several tests before actually
> =>> writing to a Compact Disk or Digital Versatile Disk, if the timing
> =>> and load response of the system is not known.
> =>> 
> =>> Is this useful?
> =>
> =>I dunno.  Before the changes did you try it - and after did you try
> it =>to see if it works?
> =>
> =>Do you actually use BB?
> =>
> =>That sounds rude, but isn't meant so.
> =>
> =>Surely only change things one step at a time - please don't break
> =>current functionality of BB to be _able_ to burn/rip etc. to not be
> =>able to do it.
> 
> It's not possible to test all of the changes I make. That's why I
> need help with the testing. And no, it's not at all rude. I do unit
> test the changes I make but it's not possible to in all cases see how
> the whole system works.
> 
> If you take a look at burning/burning.sh/dvd_image_burn, you see the 
> following line:
> 
> if ${BB_DVDBURNCMD} -dvd-compat \
>     -Z ${BBCDWRITER}=${BBBURNDIR}/$(ls ${BBBURNDIR} | grep -i
> $imagetype)
> 
> This will work fine if there is exactly one iso in the directory. If
> there are >1 then the commandline will (might?) expand to 
> 
> if growisofs -dvd-compat -Z /dev/dvd=/bburndir/f1.iso f2.iso etc...
> 
> I just need to know what the right thing to do is. Is there not a 
> specified file that we're supposed to use, or is it the case that it
> is possible that we want to use multiple iso files?
> 

I don't know - Anders will.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] I have a subversion question

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

On Fri, 5 Sep 2008 21:57:37 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> I'm new to this and I can't see it in the docs yet.
> 
> As I speak, we're at rev 508. I would like to see previous versions
> of a file. If the file hasn't been modified in a while, then I could
> look at different version for a long time before I find the last time
> that the file was modified. How do I get a list of all the versions
> where a particualr file actually changed?
> 

I usually use the web browser thing (for BB a least), as it is easy to
diff, but the svn way is:

svn log <file>

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] I have a subversion question

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

I'm new to this and I can't see it in the docs yet.

As I speak, we're at rev 508. I would like to see previous versions of a 
file. If the file hasn't been modified in a while, then I could look at 
different version for a long time before I find the last time that the 
file was modified. How do I get a list of all the versions where a 
particualr file actually changed?

-- 
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

Re: [Bashburn-info] Multiple problems in burning.sh

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

On Friday, Sep 5th 2008 at 16:20 -0000, quoth Nick Warne:

=>On Fri, 5 Sep 2008 14:20:49 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>
=>> =>Trouble is here, Steve is how to test it.  I don't have any stuff to
=>> =>burn/discs to test with?
=>> =>
=>> =>How can we test it all?
=>> =>
=>> =>Is there a switch in cdrecord & friends that goes through the
=>> motions =>(like --dry-run) and just pretends to burn something?
=>> 
=>> I see a -dummy option on cdrecord:
=>> 
=>>    -dummy The CD/DVD-Recorder will go through all steps of the
=>> recording process,  but the laser is turned off during this
=>> procedure. It is recommended to run several tests before actually
=>> writing to a Compact Disk or Digital Versatile Disk, if the timing
=>> and load response of the system is not known.
=>> 
=>> Is this useful?
=>
=>I dunno.  Before the changes did you try it - and after did you try it
=>to see if it works?
=>
=>Do you actually use BB?
=>
=>That sounds rude, but isn't meant so.
=>
=>Surely only change things one step at a time - please don't break
=>current functionality of BB to be _able_ to burn/rip etc. to not be
=>able to do it.

It's not possible to test all of the changes I make. That's why I need 
help with the testing. And no, it's not at all rude. I do unit test the 
changes I make but it's not possible to in all cases see how the whole 
system works.

If you take a look at burning/burning.sh/dvd_image_burn, you see the 
following line:

if ${BB_DVDBURNCMD} -dvd-compat \
    -Z ${BBCDWRITER}=${BBBURNDIR}/$(ls ${BBBURNDIR} | grep -i $imagetype)

This will work fine if there is exactly one iso in the directory. If there 
are >1 then the commandline will (might?) expand to 

if growisofs -dvd-compat -Z /dev/dvd=/bburndir/f1.iso f2.iso etc...

I just need to know what the right thing to do is. Is there not a 
specified file that we're supposed to use, or is it the case that it is 
possible that we want to use multiple iso files?

-- 
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