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.
Sample Output
You need to try this in vi to see what it does.

First, search (/) for a string.
For example: "/if". Now all the "if"s are highlighted.
To remove the highlighting: "/^~" .

It works because the pattern "^~" is a very unlikely pattern to find.


-5
By: mpb
2012-08-02 21:10:23

What Others Think

The proper way to take care of this issue is: :noh which stands for "no highlighting"
silbak04 · 476 weeks and 4 days ago
@silbak04: :noh won't work, certainly for any recent versions of vim. You need to type :nohls which is short for "no highlight search" :nohlsearch
flatcap · 476 weeks and 4 days ago
:noh works fine in vim 7.3.429 for me.
mrfixit42 · 476 weeks and 4 days ago
The three characters /^~ are faster to type than :noh
mpb · 476 weeks and 4 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. :-)
mpb · 476 weeks and 4 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
dstahlke · 475 weeks and 6 days 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 "/^~"
mpb · 466 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands



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: