Select-String and Grep

re: Select-String and Grep

WangFS — Fri, 30 Sep 2011 01:47:41 GMT

#grep -o '\d+' output --only-matching part of a line func how to get?

re: Select-String and Grep

Clint Boessen — Thu, 16 Sep 2010 06:56:08 GMT

Please see my howto for basic grep functionality under powershell:

clintboessen.blogspot.com/.../how-to-grep-in-powershell.html

re: your wish is our command

Hugo Eustaquio — Tue, 19 May 2009 23:53:45 GMT

I want a md5sum to use with my scripts.

re: your wish is our command

Hugo Eustáquio — Tue, 19 May 2009 23:51:22 GMT

I want a md5sum for power shell, to integrate with my scripts.

re: Select-String and Grep

Luke Breuer — Mon, 22 Dec 2008 13:19:36 GMT

Here are some performance numbers; when processing lines of text, PS appears to max out at around 4 lines/ms, whereas cmd.exe hits almost 3000 lines/ms for large files:

http://luke.breuer.com/time/item/PowerShell_pipeline_performance/527.aspx

re: Select-String and Grep

Luke Breuer — Sat, 20 Dec 2008 12:06:06 GMT

Grep is such a powerful and oft-used tool that I should think excellent support in v1 would be at the top of people's list. I guess the focus was just on management more than processing text, but please note that processing text will be VERY IMPORTANT until everything is PS. Until then, please give us a nice transition story. I'll echo the --only-matches flag, the --max-count flag, the --no-filename flag, the --count flag, and the --invert-match flag. Most of the features of grep are useful and I don't think supporting them would cost much in terms of benefit.

As an aside, is there discussion somewhere of the poor performance when, say, tailing the last million lines of a file and piping it to grep? I've resorted to cmd /c "tail ... | grep ...", but that's kludgy, due to nesting of escapes and all that fun. I tried a hack with lambdas [1], but it has two problems: it doesn't do string interpolation and some unknown problem I have yet to fully characterize. Do you guys have any story for this?

[1] http://luke.breuer.com/time/item/PowerShell_better_cmd_handling/481.aspx

re: Select-String and Grep

Adrian — Fri, 14 Nov 2008 20:51:31 GMT

I'm going to answer my own question

ipconfig | select-string "IPv4 Address" | foreach { $_.Line | where { $_ -match "(\d{1,3}.){3}\d{1,3}" } | foreach { $matches[0] } }

That was what I'm looking for but it's slightly more cumbersome than a property.

--only-matches

Adrian — Fri, 14 Nov 2008 20:39:20 GMT

What I find myself constantly wanting is a way to get the output equivalent of the --only-matches flag of grep

The documentation tantalizes you by saying...

Pattern: the string that was actually matched

But it's not true - is the expression you used, which is what you'd expect.

I'd really like to have the actual match text as a property.

e.g.

ipconfig | select-string "IPv4 Address" | foreach { $_.Line | select-string "(\d{1,3}.)\d{1,3}" | foreach { $_.Match } } | > list-of-ip-addresses.txt

re: Select-String and Grep

PeterF — Mon, 08 Sep 2008 04:49:25 GMT

The behaviour of select-string is very different from grep. Take this example using a pipe. In both a Linux OS and a Windows OS, I have three files. 2.txt found.txt and test.txt that contain the string "found":

UNIX/Linux bash shell:

# ls

2.txt found.txt test.txt

Windows PowerShell:

> ls

Directory: Microsoft.PowerShell.Core\FileSystem::C:\aa\monad_doc\test_out

Mode LastWriteTime Length Name

---- ------------- ------ ----

-a--- 8/09/2008 10:25 AM 49 2.txt

-a--- 8/09/2008 10:25 AM 49 found.txt

-a--- 8/09/2008 10:25 AM 49 test.txt

Now I want to find out which files in the folder include the string "found" in their file names:

UNIX/Linux bash shell:

# ls | grep found

found.txt

Windows PowerShell:

> ls | select-string found

2.txt:1:found

2.txt:2:his found

2.txt:3:hisfound

2.txt:4:her found

2.txt:5:herfound

found.txt:1:found

found.txt:2:my found

found.txt:3:myfound

found.txt:4:your found

found.txt:5:yourfound

test.txt:1:found

test.txt:2:my found

test.txt:3:myfound

test.txt:4:your found

test.txt:5:yourfound

bash interprets the command to mean "from all the file names returned by ls, return all instances of file names containing the string "found"

PowerShell interprets the command to mean "in all the files returned by ls, return filename - colon - instance number per file (reading from the head of the file) - colon - line containing the string "found"

Now let's dispense with the pipe and see what happens when we operate on one file only:

UNIX/Linux bash shell:

# grep found test.txt

found

my found

myfound

your found

yourfound

Windows PowerShell:

> select-string found test.txt

test.txt:1:found

test.txt:2:my found

test.txt:3:myfound

test.txt:4:your found

test.txt:5:yourfound

bash interprets the command to mean "return all lines containing the string "found" in the file test.txt"

PowerShell interprets the command to mean "return filename - colon - instance number (reading from the head of the file) - colon line containing the string "found" in the file test.txt"

This is _just_the_beginning_ of the differences between grep and select-string.

re: Select-String and Grep

PowerShell Team — Tue, 25 Mar 2008 06:51:10 GMT

> Does that mean one could use get-content -wait and pipe that to Select-String to watch a file and trigger an event when something matches?

I have not tried that but I think you'll be able to connect those dots. You'd need to run it in the background and then register for output events.

Jeffrey Snover [MSFT]

Windows Management Partner Architect

Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx