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.

Universal configuration monitoring and system of record for IT.

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



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

before writing a new script

Terminal - before writing a new script
echo -n '#!'$(which awk)
2012-02-13 12:15:41
User: SuperFly
Functions: echo which
before writing a new script

Try it this way...


There are 2 alternatives - vote for the best!

Terminal - Alternatives
:autocmd BufNewFile *.sh,*.bash 0put =\"#!/bin/bash\<nl># -*- coding: UTF8 -*-\<nl>\<nl>\"|$
2012-02-06 08:28:05
User: jlaunay
Tags: bash

or add this line to your ~/.vimrc if using vim

echo '#!'$(which bash) > script.sh
2012-02-06 08:25:27
User: sharfah
Functions: echo which
Tags: bash

Writes out the shebang line (#!/bin/bash) to the script.

{ echo -n '#!'; which bash; } > script.sh
2012-02-06 01:03:22
User: kev
Functions: echo which
Tags: bash

write first line `#!`

Know a better way?

If you can do better, submit your command here.

What others think

echo '#!/usr/bin/env bash'

Comment by tusooa 271 weeks and 3 days ago

still a bad idea.. so many useless typing.

in the worst case, open you file in vi type !!which awk and then i#!

in worst case...

Comment by makidoko 271 weeks and 2 days ago

Tusooa has the right idea. With /usr/bin/env, you get whichever version of the interpreter your environment is using, without having to think about where it is.

Comment by Fudo 271 weeks and 2 days ago

How about using vim-bashsupport?

See http://www.vim.org/scripts/script.php?script_id=365

This will automagically insert the proper lines depending on filetype. And some useful comment, and...

Comment by joedhon 271 weeks and 1 day ago

Your point of view

You must be signed in to comment.