[Bashburn-info] I'd like to propose new verbose functionality

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

The idea is that I detest GUIs that execute commandlines without telling 
you what it's doing. For example, k3b is just doing the same thing (I 
believe) that BB is doing; it runs cdrecord, mkisofs, etc, but I never 
actually see what it's doing.

Here at the company I work for, we use Perforce for our revision control. 
There's a commandline interface and also a GUI available. The Perforce GUI 
is nice because it has a little command window that tells you exactly what 
it's doing at all times.

I'd like to see BB do the same thing. Here are some options:

* It always goes to a log file. We currently already write the date? to 
$BBERRLOG. Alternatively it could just go to stdout or stderr.

* We could add a -v option to the commandline to turn on this verbose 
output.

* We could have a command option to toggle verbose in the main menu.

* We could make it a config option.

Who likes this? Who dislikes it? Are any of the above options attractive?

Don't think *how* it gets implemented. Think what you want it to do.

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