Аналог команды grep в windows

There is a command-line tool called FINDSTR that comes with all Windows NT-class operating systems (type FINDSTR /? into a Command Prompt window for more information) It doesn’t support everything grep does but it might be sufficient for your needs.

PowerShell (included as standard on Windows 7/2008R2, optional for XP/2003/Vista/2008) which includes the select-string cmdlet for this purpose.

as mentioned, findstr works fine. example :

C:>dir | findstr Windows

11/06/2013 09:55 PM Windows

answered Dec 30, 2013 at 20:07

I’m surprised no one has mentioned FINDSTR. I’m no grep poweruser, but findstr does what I need it to, filter files and stdin, with some primitive regex support. Ships with Windows and all that. (Edit: Well someone did mention findstr, It’s late I guess)

answered Sep 12, 2009 at 22:36

I also found one more way of utilizing GREP like functionality in Windows 7 and above without any extra application to install and on older systems you can use install Powershell.

In Powershell, User can use Where-Object it has quite comprehensive set of feature that provides all the functionality of GREP plus more.

Hope It helps.

answered Jul 31, 2012 at 1:13

answered Apr 21, 2014 at 9:26

UnxUtils is a great set of Unix utilites that run on Windows. It has grep, sed, gawk, etc.

answered Dec 6, 2011 at 19:26

answered Sep 13, 2009 at 4:06

You have obviously gotten a lot of different recommendations.
My personal choice for a Free, 3rd Party Utility is: Agent Ransack
Agent Ransack Download
Despite its somewhat confusing name, it works well and can be used in a variety of ways to find files.

Good Luck

answered Oct 16, 2017 at 19:42

answered Sep 14, 2009 at 21:58

answered May 17, 2011 at 18:35

answered Oct 13, 2017 at 14:07

Use Cygwin…

it has 32 and 64 bits versions
and it works fine from Windows 2000 (*)

to Windows 10 or Server 2019

I use Cygwin for a long time…

and recently tryed to substitute with Windows-Linux-Subsystems…

not for long…

I quickly went back to Cygwin again…

much more flexible, controlable and rich…
also less intrusive…

just add \bin to the path…
and you can use it anyware in Windows/Batch/Powershell…
or in a DOS-Box… or in a Powershell-Box…

Also you can install a ton of great packages
that really work… like nginX or PHP…
I even use the Cygwin PHP package in my IIS…

As a bonus wou can also use it from a bash shell…
(I think this was the original intent ;-))

answered Apr 24, 2019 at 15:44

Bare Grep is nice if you want a GUI. Gnu grep is good for CLI

answered Sep 12, 2009 at 22:11

answered Sep 12, 2009 at 22:13

We have recently used PowerGREP for some fairly advanced bulk operations on thousands of files. Including regex searching in content of PDF files, and altering PDF documents in largescale.

Its worth the money if you want to save time from manuel labour. You can try it before you buy i think.

answered Sep 12, 2009 at 22:32

If you have to use bare Windows, then in addition to the Powershell option noted above, you can use VBScript, which has decent RegEx support.

MS also has a decent scripting area on Technet with a ton of examples for administrators.

answered Sep 13, 2009 at 1:29

answered Feb 4, 2010 at 16:13

As mentioned above, the gnuwin32 project has a Windows CLI version of grep.

If you want something with a graphical interface, I would recommend the (open-source) tool AstroGrep.

answered Feb 4, 2010 at 16:20

answered Feb 4, 2010 at 16:34

answered Dec 6, 2011 at 19:22

I recommend PowerGrep

I had to do an e-discovery project several years ago. I found that fisdstr had some limitations, most especially fisdstr would eventually fail

the script had to search across thousands of files using a couple of dozen search terms/phrases.

Cygwin’s grep worked much better, it didn’t choke often, but ultimately I went to PowerGrep because the graphical interface made it much easier to tell when and where it crashed, and also it was really easy to edit in all the conditionals and output that I wanted. Ultimately PowerGrep was the most reliable of the three.

I know that it’s a bit old topic but, here is another thing you can do. I work on a developer VM with no internet access and quite limited free disk space, so I made use of the java installed on it.

Compile small java program that prints regex matches to the console. Put the jar somewhere on your system, create a batch to execute it and add the folder to your PATH variable:

JGrep.java:

package com.jgrep;

import java.io.BufferedReader;
import java.io.FileNotFoundException;
import java.io.FileReader;
import java.io.IOException;
import java.util.regex.Matcher;
import java.util.regex.Pattern;

public class JGrep {

    public static void main(String[] args) throws FileNotFoundException, IOException {
        int printGroup = -1;
        if (args.length < 2) {
            System.out.println("Invalid arguments. Usage:");
            System.out.println("jgrep [...-MODIFIERS] [PATTERN] [FILENAME]");
            System.out.println("Available modifiers:");
            System.out.println(" -printGroup            - will print the given group only instead of the whole match. Eg: -printGroup=1");
            System.out.println("Current arguments:");
            for (int i = 0; i < args.length; i++) {
                System.out.println("args[" + i + "]=" + args[i]);
            }
            return;
        }
        Pattern pattern = null;
        String filename = args[args.length - 1];
        String patternArg = args[args.length - 2];        
        pattern = Pattern.compile(patternArg);

        int argCount = 2;
        while (args.length - argCount - 1 >= 0) {
            String arg = args[args.length - argCount - 1];
            argCount++;
            if (arg.startsWith("-printGroup=")) {
                printGroup = Integer.parseInt(arg.substring("-printGroup=".length()));
            }
        }
        StringBuilder sb = new StringBuilder();
        try (BufferedReader br = new BufferedReader(new FileReader(filename))) {
            sb = new StringBuilder();
            String line = br.readLine();

            while (line != null) {
                sb.append(line);
                sb.append(System.lineSeparator());
                line = br.readLine();
            }
        }
        Matcher matcher = pattern.matcher(sb.toString());
        int matchesCount = 0;
        while (matcher.find()) {
            if (printGroup > 0) {
                System.out.println(matcher.group(printGroup));
            } else {
                System.out.println(matcher.group());
            }
            matchesCount++;
        }
        System.out.println("----------------------------------------");
        System.out.println("File: " + filename);
        System.out.println("Pattern: " + pattern.pattern());
        System.out.println("PrintGroup: " + printGroup);
        System.out.println("Matches: " + matchesCount);
    }
}

c:\jgrep\jgrep.bat (together with jgrep.jar):

@echo off
java -cp c:\jgrep\jgrep.jar com.jgrep.JGrep %*

and add c:\jgrep in the end of the PATH environment variable.

Now simply call jgrep "expression" file.txt from anywhere.

I needed to print some specific groups from my expression so I added a modifier and call it like jgrep -printGroup=1 "expression" file.txt.

answered Jan 29, 2018 at 16:09

Is there a command prompt grep equivalent for Windows 7? That is, I want to filter out the results of a command:

Bash use:

ls | grep root

What would it be from a Windows command prompt?

In your early revision you wrote MS-DOS, there’s only FIND, as far as I know. But it’s an ancient OS not used anymore.

In the Windows NT command prompt(e.g. Win2K and win XP and later, so e.g. win7,win10), you can use find and findstr and if you download GnuWin32 then grep

The basic differences are that findstr has some regular expressions support. Grep supports regular expressions best.

C:\>dir | find "abc"
C:\>dir | find /i "abc"

find /? and findstr /?shows you what the switches do.

Gnuwin32 has «packages». If you download GnuWin32, I suggest the coreutils package for a bunch of basic useful utilities you’d be familiar with, but grep isn’t in that one it’s its own package.

Added

GnuWin32’s grep, last time I checked, is old. Cygwin’s grep is far more up to date. Also bear in mind that many people use Virtual Machines rather than windows ports of *nix commands.

answered Jun 22, 2011 at 21:00

If you would rather use grep, rather than findstr, there is a single .exe file version in UnxUtils, so it’s portable and there is no need to install it, or use something like Cygwin.

I wrote a Windows alternative to grep using Hybrid Batch/JScript code. I wrote this because getting the escape characters right in the GNU Win32 grep port was a real pain. This version works much more like how you would want the GNU version to work in Windows:

@set @junk=1 /*
@cscript //nologo //E:jscript %~f0 %*
@goto :eof */

var args=WScript.Arguments, argCnt=args.Length, stdin=WScript.StdIn, stdout=WScript.StdOut;
var replaceSingleQuotes=false, printMatchesOnly=false, matchString, flagString, regex, argDx=0;

if(argCnt==0) {
    throw new Error("You must provide search criteria.");
}

flagString=""
if(argCnt>1) {
    for(var bLoop=true; bLoop&&argDx<argCnt-1; argDx++) {
        switch(args(argDx)) {
        case '-t': replaceSingleQuotes=true; break;
        case '-o': printMatchesOnly=true; break;
        case '-g': flagString+="g"; break;
        case '-i': flagString+="i"; break;
        case '-m': flagString+="m"; break;
        default: bLoop=false; break;
        }
    }
}
if(replaceSingleQuotes) {
    matchString=args(argCnt-1).replace("'", '"');
} else {
    matchString=args(argCnt-1);
}

if(printMatchesOnly) {
    while(!stdin.AtEndOfStream) {
        var sLine=stdin.ReadLine();
        if(flagString.Length) regex=new RegExp(matchString, flagString);
        else regex=new RegExp(matchString);
        var m,matches=[],startDx=0;
        while((m=regex.exec(sLine.substr(startDx))) !== null) {
            stdout.WriteLine(m[0]);
            startDx+=m.lastIndex;
        }
    }
} else {
    if(flagString.Length) regex=new RegExp(matchString, flagString);
    else regex=new RegExp(matchString);
    while(!stdin.AtEndOfStream) {
        var sLine=stdin.ReadLine();
        if(regex.test(sLine)) {
            stdout.WriteLine(sLine);
        }
    }

}

You can always find the latest version on my Gist page for this.

http://www.multireplacer.com

Multi replacer program has been prepared so that many functions can be carried out by using
command line parameters. Command line usage is seen below:

MultiReplacer [Multi Replacer File] | [Search files] | [Search folders]
[-Subs] [-NoSubs] [-IncPtr=pattern] [-ExcPtr=patterns] [-DestDir=destination]
[-DMAnyTime]
[-DMWithinanhour] [-DMToday] [-DMYesterday] [-DMThisweek] [-DMThismonth]
[-DMThisYear]
[-CDMAfter=date] [-CDMBefore=date] [-MinFileSize=bytes count]
[-MaxFileSize=bytes count]
[-Search=text] [-Case] [-NoCase] [-Regex] [-NoRegex] [-SubMatchText=text]
[-ReplaceText=text]
[-StartSearch] [-StartReplace] [-AutoClose] [-StopAfterMatchThisFile] [-StopAfterMatchAll]
[-ExtractedWordsFile=filename] [-ExtractedLinesFile=filename] [-
ReportFile=filename]

You can still use your familiar grep and other Linux commands by downloading this tool UnxUtils and add it location to your PATH environment variable

If you want to add the simplest grep to your windows environment, then navigate to c:\windows\system32 and add a little batch script by using this command:

echo findstr %1 > grep.bat

Now you can

dir | grep notepad.exe

which is really a scary mix of shit. So add another batch script for ls as explained in this post

echo dir %1 > %systemroot%\system32\ls.bat

Now things look a bit familiar

ls | grep notepad

HTH

answered Jul 4, 2017 at 8:34