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



Unix commandline history substitution like ^foo^bar BUT for multiple replacements

Terminal - Unix commandline history substitution like ^foo^bar BUT for multiple replacements
2010-04-12 11:33:08
User: brubaker
Unix commandline history substitution like ^foo^bar BUT for multiple replacements

#1 You invoked a command chain.

#2 You globaly replace the scriptnames and execute them direct

#3 The new executed command chain

[# ^foo^bar] would only replace the firts match [foo] with [bar].


There are 4 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

weeeeeeee! awesome.

Comment by linuxrawkstar 413 weeks and 6 days ago


Comment by d34dh0r53 413 weeks and 5 days ago

You can also use command history indexing to get to more than the previous command...

echo foo foo foo

foo foo foo




bar bar bar

This is an indispensable cheatsheet for bash history manipulation: http://www.catonmat.net/download/bash-history-cheat-sheet.pdf

Comment by sanmiguel 413 weeks and 3 days ago

Your point of view

You must be signed in to comment.