Capturing Groups From a Grep RegEx

by

If you’re using Bash, you don’t even have to use grep:

files="*.jpg"
regex="[0-9]+_([a-z]+)_[0-9a-z]*"
for f in $files    # unquoted in order to allow the glob to expand
do
    if [[ $f =~ $regex ]]
    then
        name="${BASH_REMATCH[1]}"
        echo "${name}.jpg"    # concatenate strings
        name="${name}.jpg"    # same thing stored in a variable
    else
        echo "$f doesn't match" >&2 # this could get noisy if there are a lot of non-matching files
    fi
done

It’s better to put the regex in a variable. Some patterns won’t work if included literally.

This uses =~ which is Bash’s regex match operator. The results of the match are saved to an array called $BASH_REMATCH. The first capture group is stored in index 1, the second (if any) in index 2, etc. Index zero is the full match.

You should be aware that without anchors, this regex (and the one using grep) will match any of the following examples and more, which may not be what you’re looking for:

123_abc_d4e5
xyz123_abc_d4e5
123_abc_d4e5.xyz
xyz123_abc_d4e5.xyz

To eliminate the second and fourth examples, make your regex like this:

^[0-9]+_([a-z]+)_[0-9a-z]*

which says the string must start with one or more digits. The carat represents the beginning of the string. If you add a dollar sign at the end of the regex, like this:

^[0-9]+_([a-z]+)_[0-9a-z]*$

then the third example will also be eliminated since the dot is not among the characters in the regex and the dollar sign represents the end of the string. Note that the fourth example fails this match as well.

If you have GNU grep (around 2.5 or later, I think, when the \K operator was added):

name=$(echo "$f" | grep -Po '(?i)[0-9]+_\K[a-z]+(?=_[0-9a-z]*)').jpg

The \K operator (variable-length look-behind) causes the preceding pattern to match, but doesn’t include the match in the result. The fixed-length equivalent is (?<=) – the pattern would be included before the closing parenthesis. You must use \K if quantifiers may match strings of different lengths (e.g. +, *, {2,4}).

The (?=) operator matches fixed or variable-length patterns and is called “look-ahead”. It also does not include the matched string in the result.

In order to make the match case-insensitive, the (?i) operator is used. It affects the patterns that follow it so its position is significant.

The regex might need to be adjusted depending on whether there are other characters in the filename. You’ll note that in this case, I show an example of concatenating a string at the same time that the substring is captured.

More Related Contents:

  1. How to get the part of a file after the first line that matches a regular expression
  2. How to process each output line in a loop?
  3. Checking if output of a command contains a certain string in a shell script
  4. Colorized grep — viewing the entire file with highlighted matches
  5. How to check if a file contains a specific string using Bash
  6. Piping tail output though grep twice
  7. Waiting for background processes to finish before exiting script
  8. How to strip out all of the links of an HTML file in Bash or grep or batch and store them in a text file
  9. How to grep for case insensitive string in a file?
  10. What does 2>&1 mean here?
  11. Input data to a shell script [closed]
  12. How to reload .bashrc settings without logging out and back in again?
  13. How do I iterate over a range of numbers defined by variables in Bash?
  14. When do we need curly braces around shell variables?
  15. Bash command line and input limit
  16. Replace one substring for another string in shell script
  17. How to assign the output of a Bash command to a variable? [duplicate]
  18. Multi-dimensional arrays in Bash
  19. How do I check if a directory exists in a Bash shell script?
  20. Checking from shell script if a directory contains files
  21. Escape dollar sign in string by shell script
  22. bash set -e and i=0;let i++ do not agree
  23. Why is “[[ 10 < 2 ]]" true when comparing numbers in bash? [duplicate]
  24. How to go to each directory and execute a command?
  25. Relative paths based on file location instead of current working directory [duplicate]
  26. Counting lines or enumerating line numbers so I can loop over them – why is this an anti-pattern?
  27. pipe stdout and stderr to two different processes in shell script?
  28. In bash, is there an equivalent of die “error msg”
  29. How do I integrate MSYS2 shell into Visual studio code on Window?
  30. How to properly nest Bash backticks

Leave a Comment