Package: osdsh
Version: 0.7.0-5wjq
Followup-For: Bug #299442
Hallo Joachim!
> have you had a chance to try Wolfram's Package[...]
I tried it now. A few issues arose:
(maybe I should file some of them as separate bugs?)
1) osdsh starts fine, except when called with option
"-m" (with /dev/mixer). Then it just shows the help
and fails to start. ALSA is working, "aumix -d /dev/mixer" too.
osdsh displays volume changes fine without use of the -m option!
2) osdsh's "-p" option is flipped (i686 too). It shows at the top if
you give "0" and at bottom when you pass it "1".
3) osdctl shows it's help screen every time it's called. It's
operating nevertheless.
4) However, there seems to be a mess with colors/styles. When I start
osdsh to show with different font, color and position,
osdctl will work correctly with options -s, -b, -l, and -x.
After turning on -c -t -m (and -a or -p, but they only give
warnings/etc. because of missing (hardware-)support) with osdctl their
messages appear at the default location with default font and color.
Using osdshconfig fixes this IIRC, but IMO one shouldn't _need_ to use
it. (And doing "Try this theme" from osdshconfig, osdsh squeakes:
"#this osdsh theme was created for osdsh-0.6.0" and "No such command"
but seems to apply the styles; not much tested here though)
5) The help screen of osdctl should, instead of:
-b (name,val) display a bar up to val, named "name"
-l (name,val) display a slider at val, named "name"
rather say:
-b name,val display a bar up to val, named "name"
-l name,val display a slider at val, named "name"
(parentheses removed) like it's shown in the man pages. First,
the parentheses will (almost certainly) cause trouble with the
shell and when escaped, the "\(" will make the name uggly ;-)
Also, having to pass two variables in one option-argument seems a bit
counterintuitive, but then it might be a lot of hard work to change
that and it's not so big trouble once one knows how to deal with it.
6) There is a funny "bug" in osdsh when displaying strings via osdctl.
Actually it may as well be a feature ;-)
How to reproduce:
(used '\n' to denote the next line in osdsh-output.
might be faulty since I have to retype it by hand and
printed spaces are so hard to spot ;-)
*)osdctl -s 'Hello world'
->writes "Hello world"
*)osdctl -s 'Hello w'
->"Hello w\nrld"
*)osdctl -s 'Now for something different'
->"Now for something different"
*)osdctl -s 'Abracadabra'
->"Abracadabra\nthing different"
*)osdctl -s 'now watch!'
->"now watch!"
*)osdctl -s 'Hell'
->"Hell\natch!"
*)osdctl -s 'Hello world'
->"Hello world\nthing different"
Why are all these second lines displayed?
Isn't there something wrong?
Because:
*)osdctl -s 'Actually, does it matter?'
->"Actually\ndoes it matter?"
*)osdctl -s 'what, would,you think, of it?'
->"what\nwould,you think, of it?"
Have fun ;-p :-D SCNR
Grüße
Georg
P.S.: I'm happy now, because I really only need osdsh
to display the volume changes.
However, for bug chasing be my guest :-D
(Apparently not so much for hunting but rather searching
if you got them all for good. ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
