Make sure a script is run in a terminal.

tty > /dev/null 2>&1 || { aplay error.wav ; exit 1 ;}
If your script needs to be run in a terminal, this line at the top will stop it running if you absent-mindedly double-click the icon, perhaps intending to edit it. (Of course this won't help with scripts that run in the background.)

By: johnraff
2009-11-04 16:18:00

2 Alternatives + Submit Alt

What Others Think

I believe you meant "exit 1" instead of "exit 0". Zero signals that there was no error.
hackerb9 · 609 weeks and 3 days ago
Well, that's up to you I suppose. I meant "no error" in the sense that the problem was with how the script was started, not with the script itself. Set it to "1" if you prefer.
johnraff · 609 weeks and 1 day ago
On reflection you're right, hackerb9. Even if the script is blameless, if the user doesn't get the result (s)he wanted then there was an error. I'll edit the line.
johnraff · 608 weeks and 5 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: