Re: [Bashburn-info] Some language and user-interface things

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

On Mon, 06 Oct 2008 16:56:23 +0200
Markus Kollmar <mar...@on...> wrote:

> Nick Warne wrote:
> > On Mon, 06 Oct 2008 15:57:45 +0200
> > Markus Kollmar <mar...@on...> wrote:
> >
> >   
> >> Nick Warne wrote:
> >>     
> >>> On Mon, 06 Oct 2008 13:44:19 +0200
> >>> Markus Kollmar <mar...@on...> wrote:
> >>>
> >>>
> >>>   
> >>>       
> >>>> --> 2.  The option
> >>>>
> >>>> bb_conf_ch_dropts=\
> >>>> "This option specifies the driver specific options used
> >>>> when burning a disc. An examples is 
> >>>> ${BBOPTIONCOLOR}burnfree${BBCOLOROFF} for
> >>>> avoiding buffer underruns. You can specify several options by
> >>>> separating them with a comma. This option is non-mandatory and
> >>>> can be skipped. Current setting is:
> >>>> ${BBOPTIONCOLOR}${BBOPT_ONE}${BBCOLOROFF}, and below is a list
> >>>> of possible options. ${bb_conf_cancel_quote}"
> >>>>
> >>>> says that below will occur a list with possible driver options,
> >>>> but there is none? Has it to be hardcoded in lang-files or is
> >>>> there a command we can get this options?
> >>>>     
> >>>>         
> >>> OK, I fixed this up too - cool feature!
> >>>
> >>> Nick
> >>>   
> >>>       
> >> Nick does this print some options on your screen?
> >> I have tested it myself but i got no option list...
> >>
> >>     
> >
> > Yes, works fine here.  Have you svn update again since?
> >
> > Nick
> >   
> Ok, sorry was my fault (not entered correct burning drive on my new 
> slackware system).
> 
> But we got the whole dump of the command - even in my case a warning 
> message, and not just the option list?

Markus,

I think that is how it used to work if I remember correctly.  I did
read the cdrecord man page, but can't see any option to just extract
'options'.

I guess we could do some sort of grep magic on the output, but then as
we don't know what make/model/CD/DVD burners/drives have with all the
possible options returned, it would be an impossible job.

Also, if somebody is nerdy enough to use BashBurn, then I think the
return output will be no problem for the user :-)

Nick
-- 
Free Software Foundation Associate Member 5508