Скачать или смотреть How to Use grep for Word Matches Without Periods as Separators

Discover how to effectively use `grep` and `awk` to perform precise word matches in your data without periods being treated as separators.
---
This video is based on the question https://stackoverflow.com/q/66921739/ asked by the user 'Shak' ( https://stackoverflow.com/u/13834461/ ) and on the answer https://stackoverflow.com/a/66921818/ provided by the user 'anubhava' ( https://stackoverflow.com/u/548225/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How can I make grep do a "word match", but without periods being treated as a word separator?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering Word Matches with grep and Avoiding Periods as Separators

If you've ever worked with text files in Unix-like systems, you know how powerful the grep command can be. However, there may come a time when you find yourself wrestling with a challenge: how to do a word match without having periods treated as word separators. In this guide, we’ll explore this common problem and provide you with effective solutions to help you retrieve the exact matches you need.

The Problem

Consider the following data set:

[[See Video to Reveal this Text or Code Snippet]]

When you try running a simple grep command, like so:

[[See Video to Reveal this Text or Code Snippet]]

You receive matches that include additional lines you don’t want, such as those containing the string with .3402. Similar results occur when using grep -F or grep -w. The challenge arises because the period (.) is treated as a word separator, causing unwanted matches.

The Solutions

Fortunately, there are effective methods to obtain the precise matches without being hindered by periods. Below, we will look at two substantial approaches: using grep with Perl-compatible regular expressions (PCRE), and an alternative using awk.

Solution 1: Using grep with PCRE

If you have gnu-grep, you can utilize its support for Perl-compatible regular expressions (PCRE). Here’s how you can do this:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

(?<!\S): This is a negative lookbehind assertion. It ensures that there is no non-whitespace character before the match.

(?!\S): This is a negative lookahead assertion. It confirms that there is no non-whitespace character after your match.

This method successfully returns results like:

[[See Video to Reveal this Text or Code Snippet]]

Solution 2: Using awk

If you prefer a more POSIX-compliant approach, awk is also a powerful alternative. Here’s a simple command you can use:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

-v s='your_string': Sets the string you want to match.

for (i=1; i<=NF; + + i): This loops through each field in the line.

The statement checks if the current field equals your specific string, and if so, it prints the entire line.

This approach will yield the same results as the first, allowing you to find your desired matches effectively regardless of the string’s position in the line.

Conclusion

With the provided methods, you can confidently utilize grep or awk to perform precise searches without being thrown off by periods in your data. Whether you opt for grep with lookarounds or a straightforward awk command, these techniques will enhance your text file processing tasks significantly. Happy grepping!