Search inside of text files

I'd say give WinGrep a shot.

If they're all in a single directory, I can see a two step process helping you out.

Step 1: Command-line

Open a CMD shell and go to the directory you're looking for. Then issue the find command:

F:\directory> find "[email protected]" *

It'll then search all files in that directory for the string you're looking for. When it finds one, it'll give you the file name, like this:

---------- MSGTRK20090603-1.LOG
2009-06-03T09:11:37.486Z,192.168

Which will tell you which file to go searching inside.

Step 2: Searching inside the file

This step you already know. The first step is just narrowing your search scope.

Use findstr at the command prompt!

C:\>findstr /?
Searches for strings in files.

FINDSTR [/B] [/E] [/L] [/R] [/S] [/I] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file]
        [/C:string] [/G:file] [/D:dir list] [/A:color attributes] [/OFF[LINE]]
        strings [[drive:][path]filename[ ...]]

  /B         Matches pattern if at the beginning of a line.
  /E         Matches pattern if at the end of a line.
  /L         Uses search strings literally.
  /R         Uses search strings as regular expressions.
  /S         Searches for matching files in the current directory and all
             subdirectories.
  /M         Prints only the filename if a file contains a match.    
  etc.


Example:
C:\>findstr /s /m [email protected] c:\temp\*.txt c:\temp\*.log
c:\temp\t\t.log
c:\temp\t\t.txt
c:\temp\t\tt.log
c:\temp\tt.txt

Redirect to a file and open in notepad:
C:\>findstr /s /m [email protected] c:\temp\*.txt c:\temp\*.log > c:\temp\myemail.txt & notepad c:\temp\myemail.txt 

You can do this one of 2 ways (well I'm sure there are more but here is what I would do)

1. Install Microsoft Desktop Search, you can do this on the server or a workstation and have it index the files. It should be able to see they are text files and index the contents. This will be the faster of the 2 ways. This is free btw.

2. Use an advanced text editor like Notepad++ or Textpad and use the file in files option which will seach though all the files in the directory. But this will take longer when you need to run the search. Notepad++ is free, Textpad has a small cost but is free to try.

If this is something you need to do frequently, I'd go with 1. If its infrequent every now and then thing, try out 2 and see if it works for you.

I like UltraEdit for this. You can tell it to seach all the files in a directory (or limit it to certain file types or any other wildcard) for a string you specify. If it finds your text in multiple files or multiple times in a file, it gives you a list of all the instances it found and clicking on one takes you to that file/location.

Use powershell then:

select-string -path c:\mylogfiledir*.log -pattern "my string"

Note that in powershell v2 you can also use the -context switch to get the lines above and below the line where the match was found

You can use ack 'A grep-like program specifically for large source trees'. Ack is like grep but written in perl (works fine on Windows). These are the reasons why it is supposedly better than grep:

1. It's blazingly fast because it only searches the stuff you want searched.
2. ack is pure Perl, so it runs on Windows just fine.
3. The standalone version uses no non-standard modules, so you can put it in your ~/bin without fear.
4. Searches recursively through directories by default, while ignoring .svn, CVS and other VCS directories. * Which would you rather type? $ grep pattern $(find . -type f | grep -v '.svn') $ ack pattern
5. ack ignores most of the crap you don't want to search * VCS directories * blib, the Perl build directory * backup files like foo~ and #foo# * binary files, core dumps, etc
6. Ignoring .svn directories means that ack is faster than grep for searching through trees.
7. Lets you specify file types to search, as in --perl or --nohtml. * Which would you rather type? $ grep pattern $(find . -name '.pl' -or -name '.pm' -or -name '*.pod' | grep -v .svn) $ ack --perl pattern Note that ack's --perl also checks the shebang lines of files without suffixes, which the find command will not.
8. File-filtering capabilities usable without searching with ack -f. This lets you create lists of files of a given type. $ ack -f --perl > all-perl-files
9. Color highlighting of search results.
10. Uses real Perl regular expressions, not a GNU subset.
11. Allows you to specify output using Perl's special variables * Example: ack '(Mr|Mr?s). (Smith|Jones)' --output='$&'
12. Many command-line switches are the same as in GNU grep: -w does word-only searching -c shows counts per file of matches -l gives the filename instead of matching lines etc.
13. Command name is 25% fewer characters to type! Save days of free-time! Heck, it's 50% shorter compared to grep -r.

I never you the windows search/find, because of things like this. I usually end up doing a search through a good old command prompt. The results are 99% much faster and more accurate then the Search/Find GUI.

c:
cd \
dir /s *.log *.tmp

You can even pipe the results into the Find command if you want to search within the results.

Don't forget Logparser can be a good Text parser/search utility as well. The 'TEXTWORD and TEXTLINE input' formats and the 'CSV and TSV input' formats are worth running the logparser -i:INPUTFORMATYOUWISHTOKNOWMOREABOUT -h 'help' call on. There are examples within the 'help' files, too.

I use Agent Ransack and it works great. It also attaches it self to the right-click menu so you can right click the folder and say Agent Ransack and it will search there. Oh and best thing, it's free.

I use this to search inside text files as well as temp folders that normal Search from Windows won't search.

Hope it helps.