commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. 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.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
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:
Cleaner with a mailto assignment in crontab (if the command fails you get an email):
MAILTO=admin@example.com
10,30,50 * * * * ping -q -c1 -w3 192.168.0.14 >/dev/null
If you want to know which values from a list are used within a file.
Here's the bash function - called goo - for lack of a better name ;)
function goo() {
perl -e 'while (my $l = <STDIN>) { foreach (sort { length($b) <=> length($a) } @ARGV) { print "$_\n" x $l =~ s/$_//ig; } }' "$@"
}
This version now adds a header with consecutive numbering.
-n switch keeps empty columns
If your distribution does not ship with a recent column version that supports -n you can use this alternative:
perl -pe 's/(^|;);/$1 ;/g' file.csv | column -ts\; | less -S
Change the delimiter to your liking.
I use this in my bashrc to expand hosts defined in ~/.ssh/config:
function _ssh_completion() {
perl -ne 'print "$1 " if /^Host (.+)$/' ~/.ssh/config
}
complete -W "$(_ssh_completion)" ssh
Here's a great article on how to setup your own ~/.ssh/config:
http://blogs.perl.org/users/smylers/2011/08/ssh-productivity-tips.html
Even faster without the need for cut... :)
Not really better - just different ;)
There's probably a really simple solution out there somewhere...