5 ms·

What do you use for grep? I tried using Powershell and did a few things with it, but while it is a great shell, the lack of good tools like grep prevented me f

What do you use for grep? I tried using Powershell and did a few things with it, but while it is a great shell, the lack of good tools like grep prevented me from being really productive.

cron 12y ago
`select-string` or it's alias `sst`. I find myself filtering collections of objects far more frequently then grepping lines when using powershell.
nailer 12y ago
I use `where` for finding stuff, but that's based on structure rather than scraping.
pjc50 12y ago
I've ended up with Select-String "pattern" -Path file.txt | ForEach-Object { Write-Output $_.Line } | Out-File t.txt Slightly Heath Robinson, but by default PS will truncate lines to terminal width, even when writing to a file, which is a disaster for any kind of subsequent machine processing.
- Raesan 12y ago
  You could also use either of these: (Select-String "pattern" -Path file.txt).Line > t.txt Select-String "Pattern" -Path file.txt | Select-Object -ExpandProperty Line > t.txt Or equivalent to the second example but with shortcuts: sls pattern -path file.txt | select -exp line > t.txt
- hug 12y ago
  For the uninitiated this looks completely barbaric, but makes a whole lot of sense when you consider that PS is built around an object-based pipeline. 'Select-String' in PS doesn't actually return a string, but a 'MatchInfo' object, which contains more properties -- 'linenumber', 'context', etc, as well as the 'line' property which contains the actual matched lines as strings. The default output from any part of the pipeline is a human-readable/terminal-display-compatible representation of the object's commonly used properties, thus the truncation. As an aside, you can replace the foreach with select-object for an efficiency gain: sls "Pattern" file.txt | select -exp line | out-file t.txt
  - ygra 12y ago
    You also don't technically need to go through Select-String if all you care about is the line itself: (gc file.txt) -match "Pattern" | Out-File t.txt Comparison operators that get an array as their left argument return the items where the comparison returns true.
- bgilroy26 12y ago
  Today, I learned "Heath Robinson" is British English for "Rube Goldberg" http://en.wikipedia.org/wiki/W._Heath_Robinson http://en.wikipedia.org/wiki/W._Heath_Robinson
rudolf0 12y ago
Default Windows shell also has `findstr`, which works very similarly to grep. It's also quite fast.

What do you use for grep? I tried using Powershell and did a few things with it, but while it is a great shell, the lack of good tools like grep prevented me from being really productive.

cron 12y ago

`select-string` or it's alias `sst`. I find myself filtering collections of objects far more frequently then grepping lines when using powershell.

nailer 12y ago

I use `where` for finding stuff, but that's based on structure rather than scraping.

pjc50 12y ago

I've ended up with Select-String "pattern" -Path file.txt | ForEach-Object { Write-Output $_.Line } | Out-File t.txt Slightly Heath Robinson, but by default PS will truncate lines to terminal width, even when writing to a file, which is a disaster for any kind of subsequent machine processing.

Raesan 12y ago
You could also use either of these: (Select-String "pattern" -Path file.txt).Line > t.txt Select-String "Pattern" -Path file.txt | Select-Object -ExpandProperty Line > t.txt Or equivalent to the second example but with shortcuts: sls pattern -path file.txt | select -exp line > t.txt
hug 12y ago
For the uninitiated this looks completely barbaric, but makes a whole lot of sense when you consider that PS is built around an object-based pipeline. 'Select-String' in PS doesn't actually return a string, but a 'MatchInfo' object, which contains more properties -- 'linenumber', 'context', etc, as well as the 'line' property which contains the actual matched lines as strings. The default output from any part of the pipeline is a human-readable/terminal-display-compatible representation of the object's commonly used properties, thus the truncation. As an aside, you can replace the foreach with select-object for an efficiency gain: sls "Pattern" file.txt | select -exp line | out-file t.txt
- ygra 12y ago
  You also don't technically need to go through Select-String if all you care about is the line itself: (gc file.txt) -match "Pattern" | Out-File t.txt Comparison operators that get an array as their left argument return the items where the comparison returns true.
bgilroy26 12y ago
Today, I learned "Heath Robinson" is British English for "Rube Goldberg" http://en.wikipedia.org/wiki/W._Heath_Robinson http://en.wikipedia.org/wiki/W._Heath_Robinson

rudolf0 12y ago

Default Windows shell also has `findstr`, which works very similarly to grep. It's also quite fast.