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.
commandlinefu.com 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.
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.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
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:
function red_error {
"$@" 2> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done)
}
Then for example:red_error tar tvf some_file.tgz
bind 'RETURN: "\e[1~error \e[4~\n"'
See http://superuser.com/questions/117227/a-command-before-every-bash-command for more infoexec 3> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done)
some_command 2>&3
stderr from some_command will be displayed in red. This opens file handle #3 and pipes it to the subshell until that file handle is closed with exec 3>&-exec 2> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done)
Will make the shell do exectly what is wanted. all stderr displays in red and stdout displays normally for the shell and commands executed in the shell. Unfortunately is also has the effect of not displaying the prompt and any input until input is completed. Anyone know how to get around this?