Agile Zone is brought to you in partnership with:

Full-time developer on a small team. Writing great specs and code, delivered on time. Chase is a DZone MVB and is not an employee of DZone and has posted 54 posts at DZone. You can read more from them at their website. View Full User Profile

Using Grep from Inside Vim

09.24.2013
| 3804 views |
  • submit to reddit

"This is my rifle. There are many like it, but this one is mine." - Rifleman’s Creed

There are a thousand ways to grep over files. Most developers I have observed keep a separate command line open just for searching. A few use an IDE that has file search built in. Personally, I use a couple of Vim macros.

In Vim, you can execute a cross-file search with something like :vimgrep /dostuff()/j ../**/*.c. I don’t know about you, but the first time I saw that syntax my brain simply refused.

Instead, I have the following in my .vimrc file:

" opens search results in a window w/ links and highlight the matches
command! -nargs=+ Grep execute 'silent grep! -I -r -n --exclude *.{json,pyc} . -e <args>' | copen | execute 'silent /<args>'
" shift-control-* Greps for the word under the cursor
:nmap <leader>g :Grep <c-r>=expand("<cword>")<cr><cr>

The first command is just a simple alias for the above mentioned native grep. Like all custom commands, it must start with a capital letter (to differentiate it from native commands). You simply type :Grep foobar and it will search in your current directory through all file extensions (except .json and .pyc -- you can add more to the blacklist).

It also displays the results in a nice little buffer window, which you can navigate through with normal HJKL keys, and open matches in the main editor window.

vim Grep

The second line is a key mapping that will grep for the word currently under the cursor. You can just navigate to a word and hit Leader-g to issue the grep command.



Published at DZone with permission of Chase Seibert, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)