public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: "Speakup List" <speakup@speech.braille.uwo.ca>
Subject: Sound on command exit
Date: Fri, 14 Apr 2000 23:50:39 -0700	[thread overview]
Message-ID: <000c01bfa6a6$eb5d3780$fa115b80@wang> (raw)

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

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




             reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Victor Tsaran [this message]
 ` Sebastian Taralunga
   ` Janina Sajka
   ` Victor Tsaran
 ` Janina Sajka
 Martin G. McCormick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000c01bfa6a6$eb5d3780$fa115b80@wang' \
    --to=vtsaran@nimbus.ocis.temple.edu \
    --cc=speakup@speech.braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).