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

vi: search string "^~" (unlikley pattern). Useful after search/highlight when you want to drop the highlighting.

Terminal - vi: search string "^~" (unlikley pattern). Useful after search/highlight when you want to drop the highlighting.
2012-08-02 21:10:23
User: mpb
vi: search string "^~" (unlikley pattern). Useful after search/highlight when you want to drop the highlighting.

When searching in vi, the search string gets highlighted but the highlighting can become a nuisance.

By searching for the very unlikely pattern "^~" the highlighting is effectively switched off.


There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

The proper way to take care of this issue is:


which stands for "no highlighting"

Comment by silbak04 220 weeks and 6 days ago



won't work, certainly for any recent versions of vim. You need to type


which is short for "no highlight search"

Comment by flatcap 220 weeks and 6 days ago

:noh works fine in vim 7.3.429 for me.

Comment by mrfixit42 220 weeks and 6 days ago

The three characters /^~ are faster to type than :noh

Comment by mpb 220 weeks and 5 days ago

@silnak04 What is a "proper way" ? The expression: "There is more than one way to skin a cat." seems appropriate.

What can I tell you? "/^~" works very well and I have used it for years.

Anyway, thank you for suggesting ":soh". It's useful to know another way to skin this particular cat. :-)

Comment by mpb 220 weeks and 5 days ago

Put this in your .vimrc so that pressing enter (while in edit mode) will toggle highlighting. Normally enter doesn't really do anything except move the cursor down a line.

" toggles search highlighting

nnoremap / :set hls/

nnoremap n :set hlsn

nnoremap N :set hlsN

nnoremap :set invhls

Comment by dstahlke 220 weeks and 1 day ago

@dstahlke Thank you for sharing that .vimrc idea.

I personally avoid making too many configuration files because I work on multiple machines and it's a bit of a nuisance having to reset all my preferred settings in config files on each new machine.

This is another reason why I like the simple solution of "/^~"

Comment by mpb 210 weeks and 2 days ago

Your point of view

You must be signed in to comment.