Skip to main content

Handy vi tip - opening a list of files from a grep command

My primary text editor of choice is VI (actually, vim) - a console-based text editor that I use via SSH on the various linux servers that I work with. There's also a windows version available that I use occasionally, but I'm more likely to use textpad for that work.

Anyways, vim when used via a console on a linux server is really quite powerful. Here's a handy tip - suppose you're working with a large number of files nested within multiple subdirectories - and you need to edit all the files that contain a certain string. Perhaps you need to open and edit every file that uses a certain javascript file (let's call it 'example.js').

First, you can find all the files that have this string in them by using grep to search recursively for it:
grep -r 'example.js' *

This will return a long list of files with the text where that string was found. But what you really need is just the file names that have the string. This can be done by adding the "-l" option to your grep command:
grep -rl 'example.js' *

Now you have your list of files, and you need some way to tell vi to open them. This is accomplished by simply putting the grep command within "`" characters:
vi `grep -rl 'example.js' *`

You can find that key at the top left of your keyboard. And voila - vi opens all the files, and you can edit that one at a time!
Labels:

Comments

Post a Comment

Popular posts from this blog

Another VI tip - using macros, an example

God I love VI. Well, actually, vim but whatever. Here's another reason why. Suppose you need to perform some repetitive task over and over, such as updating the copyright date in the footer of a static website. (Yes, yes I know you could do a javascript thing or whatever, just bear with me.) Of course you could just search and replace in some text editor, changing "2007" to "2008" (if you're stupid) - and you'll end up with a bunch of incorrect dates being changed, most likely. What you need to do is only change that date at the bottom. And suppose that because of the formatting, you can't use the "Copy" part of the string in a search replace - perhaps some of the pages use "©", some spell out "Copyright" etc. This is where vi macros come in handy. A macro in vi is exactly what you expect, it records your actions and allows you to play them back. To start recording, press q followed by a character to use to "stor...
6 comments
Read more

Cleaning content from OpenOffice using Perl

Open office is great software for a number of things - I use it as my office software instead of paying a premium for Microsoft office. But one thing it's not so hot at is converting documents to clean HTML. And one of the main things I use it for is adding content to sites that clients send me in word files or excel spreadsheets. Of course, you can always cut and paste, but that loses a lot of formatting. For example, if the content uses a lot of italics, bold text, etc. it can be a huge pain to go back and put all that back in. Another common situation is a client sending some sort of tablular data in a spreadsheet - for example a list of events. It's the kind of data that can change a lot, and it also needs to be in a table with some decent formatting to be usable. Doing it manually is a lot of grunt work. But grunt work is what computers excel at, and I'm not very good at. So I've developed a number of perl scripts to help streamline this kind of job. I'll go ...
3 comments
Read more

Using FIle FIlters in FileZilla

Here's a handy tip for situations when you want to download a large number of files - but only of a certain type. For example, perhaps you want to download all the PHP files from a largish website, scattered through many subdirectories. Perhaps you're making a backup and don't want any image files, etc. FileZilla (still the best FTP in my opinion) has a handy feature called filename filters - located under the Edit menu. Here you can set various filters that filter out files based on their filename. Took me a minute to figure that out - you're saying show only PHP files, rather you're saying filter out files that do not have ".php" as their suffix. For some reason, that seems a little backwards to me, but whatever. It works quite well. You can also check whether the filter applies only to files, only to directories - or both. In this example, you'd want to check only files, as otherwise you won't see any directories unless they happen to end in...
1 comment
Read more