As a naive first-time user, I ran jac for the first
time without any options. jac decided the right thing
for me was a config file that specified "/dev/cdrom" as
my CD device. As it happens, this isn't the right
thing for me -- /dev/cdrom isn't hooked up to my
soundcard, so I use /dev/cdrom2.
But once I figured out about the -w option (why not -d
like every other CD player in the universe?), I ran
"jac -w /dev/cdrom2", and that works. Well, sort of.
Trouble is, there's a long delay before jac actually
does anything to /dev/cdrom2. strace reveals that it's
attempting to open /dev/cdrom, which blocks for several
seconds before returning with a "No medium found" error.
I think there are at least three distinct bugs here:
* automatically creating a config file just seems
like the wrong thing to do, especially since (in
my case) that config file has an incorrect
setting (cdrom=/dev/cdrom)
* using that incorrect setting from the config file
even though I overrode it on the command line
* not reporting the failed attempt to access
/dev/cdrom -- if there had been a "/dev/cdrom: No
medium found" message on the console, then I
wouldn't have had to resort to strace!
To compound the annoyance factor, if I delete
~/.jac/jac.config and rerun with "-w /dev/cdrom2", it
*still* creates a config file for me -- with the
*wrong* cdrom setting! Argghh! IMHO no console
program should *ever* create a config file without
being explicitly told to.
