Suggested modification/extension of beep

[Harald Becker]

Hallo Jim!

On 19.02.2010 18:53, Cathey, Jim wrote:
> I imagine that the original beep was used in a pipeline,
>   
Yes, according to the manpage of the original beep and other docs it
seems to be that this was the authors original indention.

> slowthing | beep doo-dah | nextthing
>   
The original beep has two command line arguments -c and -s to enable
this type of usage to trigger the sound display. But this functionality
is not implemented in the busybox applet. It's just noted as TODO in a
comment.

... if anybody is interested in this feature I can add in this stuff
into busybox beep. I'm thinking about forking and sending trigger events
via a pipe to the child. This way can pass on all informations through
to stdout without loosing any time due to the tune play. Interested?

> I would suggest the ability to do something like
>
> <music.txt awk -f converter | beep -i -
>   
Yes, I thought about this, but it still adds some extra code to the
busybox binary. Try the following, it should allow tunes of unlimited
length, if you like:

<music.txt awk -f  converter | xargs -s 1000 beep

or if you want to repeat forever:

while true; do <music.txt awk -f converter; done | xargs -s 1000 beep

or maybe better:

while true; do <music.txt awk -f converter | xargs -s 1000 beep; sleep
2s; done

... all without extra code in the busybox binary ... and I think busybox
tries to keep things small.

Harald