Login

Command line quick tips: Searching with grep

<div>If you use your Fedora system for more than just browsing the web, you have probably needed to search for text in your files. For instance, you might be a developer that can’t remember where you left some code snippet. Or you might be looking for a setting stored in your system configuration files. Whatever the reason, there are plenty of ways to search for text on your Fedora system. This article will show you how, including using the built-in utility grep.
 
<h2>Introducing grep</h2>
The grep utility allows you to search for text, or more specifically text patterns, on your file system. The name grep comes from global regular expression print. Yikes, what a mouthful! This is because a regular expression (or regex) is a way of defining text patterns.
The grep utility lets you find and print out matches on these patterns — thus the name. It’s a powerful system, and you can even find it in modern code editors like <a href="https://fedoramagazine.org/using-visual-studio-code-fedora/">Visual Studio Code</a> or <a href="https://fedoramagazine.org/install-atom-fedora/">Atom</a>.
<h2>Regular expressions</h2>
Harnessing all the power of <a href="https://en.wikipedia.org/wiki/Regular_expression">regular expressions</a> is a topic bigger than this article, for sure. The simplest kind of regex can be just a word, or a portion of a word. That pattern is simply “the following characters, in the same order.” The pattern is searched line by line. For example:
<ul>
<li>pciutil – matches any time the 7 characters pciutil appear together — including pciutil, pciutils, pciutil123, and foopciutil.</li>
<li>^pciutil – matches any time the 7 characters pciutil appear together immediately at the beginning of a line (that’s what the ^ stands for)</li>
<li>pciutil$ – matches any time the 7 characters pciutil appear together immediately before the end of a line (that’s what the $ stands for)</li>
</ul>
More complicated expressions are also possible. Special characters are used in a regex as wildcards, or to change the way the regex works. If you want to match on one of these characters, use a \ (backslash) before the character.
For instance, the . (period or full stop) is a wildcard that matches any single character. If you use it in the expression pci.til, it matches pciutil, pci4til, or pci!til, but does not match pcitil. There must be a character to match the . in the regular expression.
The ? is a marker in a regex that marks the previous element as optional. So if you built on the previous example, the expression pci.?til would also match on pcitil because there need not be a character between i and t for a valid match.
The + and * are markers that stand for repetition. While + stands for one or more of the previous element, * stands for zero or more. So the regex pci.+til would match any of these: pciutil, pci4til, pci!til, pciuuuuuutil, pci423til. However, it wouldn’t match pcitil — but the regex pci.*til would.
<h2>Examples of grep</h2>
Now that you know a little about regex, let’s put it to work. Imagine that you’re trying to find a configuration file that mentions a user account jpublic. You tried a bunch of files already, but none were the correct one, and you’re sure it’s there. So, try searching the /etc folder (using sudo because some subfolders are not readable outside the root account):
<pre class="wp-block-preformatted">$ sudo grep -r jpublic /etc/</pre>
The -r switch searches the folder recursively. The utility prints a list of matching files, and the line where the hit occurred. In most modern terminal environments, the hit is color highlighted for better readability.
Imagine you have a much larger selection of files in /home/shared and you need to establish which ones mention the name MacNulty. However, you’re not sure whether the capitalization will be consistent, and you’re just looking for names of files, not the context. Also, you believe someone may have misspelled the name as McNulty in some places.
Use the -l switch to only output filenames with a match, a ? marker for optional a in the name, and -i to make the search case-insensitive:
<pre class="wp-block-preformatted">$ sudo grep -irl 'ma\?cnulty' /home/shared</pre>
This command will match on strings like Macnulty, McNulty, Mcnulty, and macNulty with no problem. You’ll get a simple list of filenames where the match was found in the contents.
These are only the simplest ways to use grep and regular expressions. You can learn a lot more about both using the info grep command.
<h2>But wait, there’s more…</h2>
The grep command is venerable but in some situations may not be as efficient as newer search utilities. For instance, the ripgrep utility is engineered to be a fast search utility that can take the place of grep. We covered ripgrep as part of an <a href="https://fedoramagazine.org/oxidizing-fedora-try-rust-applications-today/">article on Rust and Rust applications</a> previously in the Magazine:
<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-fedora-magazine">
<div class="wp-block-embed__wrapper">
<blockquote class="wp-embedded-content" data-secret="0fpvhDfUAm"><a href="https://fedoramagazine.org/oxidizing-fedora-try-rust-applications-today/">Oxidizing Fedora: Try Rust and its applications today</a></blockquote>
</div>
</figure>
It’s important to note that ripgrep has its own command line switches and syntax. For example, it has simple switches to print only filename matches, invert searches, and many other useful functions. It can also ignore based on .rgignore files placed in any subdirectories. (It’s also noteworthy that the -r switch is used differently for ripgrep, because it is automatically recursive.)
To install, use this command:
<pre class="wp-block-preformatted">$ sudo dnf install ripgrep</pre>
To explore the options, use the manual page (man rg). You’ll find that many, but not all, options are the same as grep.
Have fun searching!
<hr class="wp-block-separator" />
</div>

https://www.sickgaming.net/blog/2019/08/...with-grep/

xSicKxBot