Simple Interrupt Driven Multitasking with scripts
2009/08/05 Leave a comment
Compiling. Searching. Downloading with wget. They take a long time and are kind of boring to stare at. You have two choices. Choice one is to follow the xkcd model:
But once in a while, you actually have some other stuff to do. Maybe if you had a few minutes you could go a few emails closer to Inbox Zero or you could go watch something to make you smarter or go read something. Either way, if you’re like me and that guy from Momento and you try to do something else useful while your computer is working you will immediate forget that it was off doing your bidding and you will stumble across the idle terminal hours/days later.
Here’s a really quick solution. Put this script in your path somewhere.
if [ $(uname) = "Darwin" ] ; then
# osascript doesn't allow you to interact with the UI so just raise the terminal
osascript < /dev/null 2>&1
elif [ $(uname) = "Linux" ] ; then
zenity --title "Finished" --info --text "I'm done doing what you asked." > /dev/null 2>&1
elif [ $(uname) = "Cygwin" ] ; then
echo "Left as an exercise for the reader. Helpful hints may be found at http://store.apple.com and http://ubuntu.com"
echo "Unknown platform: $(uname)"
I call it fin like that classy word at the end of old movies.
Then when you start a long running command run it like this:
bash$ go-search-my-whole-harddrive.sh ; fin
bash$ compile-my-kernel.sh ; fin
Then, when your thing is done, whether it worked or not, you will get some sort of indication that its done and you can get back to what you were doing.
I have really started to love this little script the last few days. One thing though, make sure that the other thing you start to do while waiting is an easily interruptable task or your brain will explode when the indication pops up. No one likes brain explosions.