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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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



Add timestamp to history

Terminal - Add timestamp to history
2009-05-12 14:36:42
User: fritz_monroe
Functions: export
Add timestamp to history

History usually only gives the command number and the command. This will add a timestamp to the history file.

Note: this will only put the correct timestamp on commands used after the export is done. You may want to put this in your .bashrc


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Thanks, I really like this.

Comment by anzan 372 weeks and 3 days ago

Must replace ? by "

Comment by aurium 372 weeks and 3 days ago

Hmm, that's strange, I know I put quotes there.

Comment by fritz_monroe 372 weeks and 3 days ago

worth a 10 up, definitely!!

Comment by icetek 372 weeks and 2 days ago

Great one.. thanks for this from your hidden treasury..

Comment by mohan43u 372 weeks ago

Nice one. Older commands in history do get correct-looking timestamps on my machines (Debian Lenny bash 3.2.39 and Mac OS X 10.5.6 bash 3.2.17).

Comment by gthb 371 weeks and 6 days ago

fritz- you can edit your command to replace the questions-marks by quotes...

I'll vote up when its fixed.

Comment by Iftah 371 weeks and 5 days ago

All fixed. This is my first command submitted, I didn't know they were editable.

Comment by fritz_monroe 371 weeks and 5 days ago

Wonderful. Goes into my ~/.bashrc straight away.

Comment by sunny256 371 weeks ago

you can try this free http://www.online-code.net/unix-timestamp.html">online timestamp converter to get a unix time.

Comment by JonyGreen 41 weeks and 2 days ago

Your point of view

You must be signed in to comment.