Suppress output of loud commands you don't want to hear from

function quietly () { $* 2> /dev/null > /dev/null; };
Suppresses all output to /dev/null. This could be expanded to check for a -l command line option to log the stderr to a file maybe -l file or -l to log to default quietly.log. I'm finding that I use it more often than one would think.
Sample Output
hostname User$ quietly wget
hostname User$ _

2011-10-02 05:02:48

2 Alternatives + Submit Alt

What Others Think

less verbose to do it like >/dev/null 2>&1
TheMightyBuzzard · 567 weeks ago
Wow, that's a good idea. A few things, though. You need to quote $* just in case the command has a space in it. Shorten the redirects as TheMightyBuzzard says. Shorten the name to something simple, maybe 'q' (too much typing otherwise :-) function q () { "$*" > /dev/null 2>&1; }; Of course in bash, you don't need the keyword 'function'! q() { "$*" > /dev/null 2>&1; };
flatcap · 566 weeks and 6 days ago
fantastic, i have created 2 aliases for me. one for total silence, the other just redirects err to out for easy grepping ;) function q () { $* 2>&1 ; } function qq () { $* 2> /dev/null > /dev/null; } PS: I do not think quotes are necessary or even good.
oernii3 · 566 weeks and 5 days ago
* without quotes fails, if there are spaces in the command or its arguments. $* with quotes "expands to a single word with the value of each parameter separated by the first character of the IFS special variable." (man bash). So it tries to run the whole command-line as a command name. So, the only valid option here is "$@". It expands to a list of quoted words, just like the original.
wipu · 566 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: