What's this?

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.

Get involved!

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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Search commandlinefu and view syntax-highlighted results in vim

Terminal - Search commandlinefu and view syntax-highlighted results in vim
cmdfu(){ local t=~/cmdfu;echo -e "\n# $1 {{{1">>$t;curl -s "commandlinefu.com/commands/matching/$1/`echo -n $1|base64`/plaintext"|sed '1,2d;s/^#.*/& {{{2/g'>$t;vim -u /dev/null -c "set ft=sh fdm=marker fdl=1 noswf" -M $t;rm $t; }
2012-02-21 05:43:16
User: AskApache
Functions: echo rm sed vim
Search commandlinefu and view syntax-highlighted results in vim

Here is the full function (got trunctated), which is much better and works for multiple queries.

function cmdfu () {

local t=~/cmdfu;

until [[ -z $1 ]]; do

echo -e "\n# $1 {{{1" >> $t;

curl -s "commandlinefu.com/commands/matching/$1/`echo -n $1|base64`/plaintext" | sed '1,2d;s/^#.*/& {{{2/g' | tee -a $t > $t.c;

sed -i "s/^# $1 {/# $1 - `grep -c '^#' $t.c` {/" $t;



vim -u /dev/null -c "set ft=sh fdm=marker fdl=1 noswf" -M $t;

rm $t $t.c


Searches commandlinefu for single/multiple queries and displays syntax-highlighted, folded, and numbered results in vim.


There are 29 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Depending on your ~/.vimrc it may throw some errors. I added a "-u NONE"-switch to the vim invocation and the "noswf"-option to avoid having a swapfile generated (which won't be deleted when you mess up vim). I like this one. Very conveniently formatted output.

Comment by disKoma 313 weeks and 4 days ago


Nice, I like the noswf. My vimrc is awesome but that's a good idea too. the vim -u NONE will work but will throw an error as its looking for a file. The solution is vim -u /dev/null

Comment by AskApache 313 weeks and 4 days ago

I updated the function to reflect your suggestions..

Comment by AskApache 313 weeks and 4 days ago

for ubuntu users is needed the -L option in curl call for the redirected response of commandlinefu


curl -L -s "commandlinefu.com/commands/matching/$1/` ....

Comment by horaciod 312 weeks ago

@AskApache Cool. I tried it out, but for quick reading, even with mapped to toggle folds, I decided to stick with mine :)

Comment by expelledboy 303 weeks and 4 days ago

...even with space mapped to toggle folds... didnt know there was formatting rules in comments?

Comment by expelledboy 303 weeks and 4 days ago

Your point of view

You must be signed in to comment.