From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out1.bellatlantic.net([199.45.39.156]) (3275 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Sat, 15 Apr 2000 12:22:41 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from adsl-151-200-20-29.bellatlantic.net (adsl-151-200-20-29.bellatlantic.net [151.200.20.29]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with ESMTP id MAA08466; Sat, 15 Apr 2000 12:22:35 -0400 (EDT) Received: from localhost (janina@localhost) by adsl-151-200-20-29.bellatlantic.net (8.9.3/8.8.7) with ESMTP id MAA05770; Sat, 15 Apr 2000 12:22:58 -0400 X-Authentication-Warning: adsl-151-200-20-29.bellatlantic.net: janina owned process doing -bs Date: Sat, 15 Apr 2000 12:22:58 -0400 (EDT) From: Janina Sajka X-Sender: janina@adsl-151-200-20-29.bellatlantic.net To: speakup@braille.uwo.ca cc: Speakup List Subject: Re: Sound on command exit In-Reply-To: <000c01bfa6a6$eb5d3780$fa115b80@wang> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: Victor: This is excellent. But how do we generalize this? What is the correct syntax to set up our bash (or whatever) environment to automatically append a '; $sound_command' to whatever command we might type? I know we can easily customize with aliases. Is that the best solution? It might be, because that way we could assign a particular sound for a particular command. Hmmm. And shouldn't we be able to somehow indicate the console involved with a variable? Were I come from, we call these kinds of sounds earcons, by the bye. On Fri, 14 Apr 2000, Victor Tsaran wrote: > Hello, listers! > Some of you have asked previously whether it is possible to have some sort > of beep after certain command exits or certain task terminates. Yesterday I > was playing around with Linux with another friend of mine, Luke Davis, who > is yet another Linux user from Philadelphia. Accidentally, we recalled that > Unix allows one to specify several commands on a single command line by > dividing these commands with a semicolon. So, for instance, to run pine > after your lynx exits you could enter: > > lynx; pine > > The Pine would fire up as soon as you quit Lynx. that opens a lot of > interesting possibilities for providing temporary sound solutions to > indicate termination of a background task or any other event. You could > either run `play' command with your beloved .wav file on the command line or > you could create a very short script called beep and exploit it. > Say, we have a file called beep_when_you_re_done.wav and you'd like to know > when your kernel finishes compiling. You might enter: > > make bzImage output.txt 2>&1 &; play beep_when_you_re_done.wav > > Now you can safely switch to another console and do other things. When "make > bzImage" is finished, it will play the file. > > Hope this can help someone. > Regards, > Victor > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Janina Sajka, Director Information Systems Research & Development American Foundation for the Blind (AFB) janina@afb.net