Written by andrewfenn the 16 Oct 08 at 22:21.
Category: Usability.
Related project:
Nothing/Others.
Status: New
Rationale
I want something that I can turn on which will give me an audio beep (or any sound I want) when the command has finished.
So if I type:
sudo apt-get install x y z
make
pbuilder update
or anything which takes years to complete, when I gets to
user@computer:~/home/user/$
It will beep to let me know. This would free me up to do other things while I am waiting and not having to see looking at the screen every 10 seconds to keep if a command finished.
It's not an ugly hack. The whole philosophy of *NIX tools is to string together simple tools to create powerful results. Eldmannen's solution is a great example of that.
I actually think this is a great idea. Maybe the best way would be to prepend/append a command in front of any commands executed in shell? (so append echo \b or whatever works)
You can do it yourself - just add '^G', or '\007' to the beginning of your $PS1 variable.
Every time commandline is drawn, you'll get the beep, or whatever signal you set in the terminal.
If it beeps every single time you run a command, it will drive you nuts, because it will beep all the time.
Most commands execute instantly in 0 seconds, with the exception of apt-get.
It might not drive you nuts if you can set it to a click sound instead of a beep. Even a single beep drives me insane, but a clicking sound would be fine.
His not asking for it enabled by default anyway. He just wants a way. So not sure why people are voting this down. If support doesn't already exist, its not difficult to add to the code if its not (I know, because 2 years ago I modified the bash code on a script kiddie wargames servers so that people would have troubles deleting the annoying britney spears midi playing in the background. And I suck at coding, so I know its not hard).