<\/span><\/h2>\nRegex, short for regular expression, is a sequence of characters that define a search pattern for text manipulation or pattern matching. In Bash, regex is used within commands like grep<\/strong>, sed<\/strong>, awk<\/strong>, and even within parameter expansions and conditional expressions. A regular expression comprises one or more elements such as:<\/p>\n\n- Character set: <\/strong>The character set in regex is a group of specific characters that are treated as their literal meaning. They don\u2019t have any special meaning or function with the regex. For example, if you include the character set [abc]<\/strong> in a regex, it will match any occurrence of \u2018a\u2019, \u2018b\u2019, or \u2018c\u2019 in the text.<\/li>\n
- Anchors: <\/strong>Anchors in regex are special symbols used to mark specific positions in the text where the pattern should match. They don\u2019t represent actual characters but rather indicate where the pattern begins or ends within the text. Two common anchors in regex are caret (^), <\/strong>and dollar sign($).<\/strong><\/li>\n
- Modifiers: <\/strong>Modifiers in regex are special symbols or characters that expand or narrow the range of text that the regex pattern can match. Some common modifiers in regex include \u2018*\u2019, \u2018+\u2019, \u2018?\u2019,<\/li>\n<\/ul>\n
<\/span>Types of Regex in Bash<\/span><\/h3>\nIn Bash, there are two<\/strong> types of regular expressions (regex) mostly used:<\/p>\n\n- Basic Regular Expression (BRE):<\/strong> BRE is the default regex type used in many traditional Unix utilities like grep, sed, <\/strong>and awk.<\/strong> In BRE, certain metacharacters (such as
?<\/code>, +<\/code>, |<\/code>, and ()<\/code>) are treated as literals unless escaped with a backslash \\<\/code>. BRE is suitable for basic pattern-matching tasks and is widely supported across Unix-based systems.<\/li>\n- Extended Regular Expression (ERE):<\/strong> ERE is an enhanced version of BRE that offers a broader range of metacharacters and features. In ERE, metacharacters such as
?<\/code>, +<\/code>, |<\/code>, and ()<\/code> are interpreted with their special meanings by default, without needing to escape them. ERE supports additional features like quantifiers (?, +, {}) and backreferences (\\1, \\2, etc.). Utilities like grep -E <\/strong>(or egrep<\/strong>) and sed -E<\/strong> explicitly support EREs. ERE offers shorter and more expressive regex patterns as compared to BRE. This makes ERE suitable for more complex pattern matching as well as text manipulation tasks.<\/li>\n<\/ol>\n<\/span>Metacharacters in Bash Regex<\/span><\/h2>\nMetacharacters are special characters in regex that enable users to perform powerful operations like pattern matching, substitution, and text manipulation.<\/p>\n
Here are some metacharacters commonly used in\u00a0 regex:<\/p>\n
\n
\n\n\nType<\/strong><\/th>\nMetacharacter<\/strong><\/th>\nDescription<\/strong><\/th>\n<\/tr>\n\nWildcard Characters<\/strong><\/td>\n*<\/strong><\/td>\nMatches zero or more occurrences of the preceding character. For instance, * .txt<\/strong> matches all the files with the “.txt” extension.<\/td>\n<\/tr>\n\n? <\/strong><\/td>\nMatches any single character. For example, file?.txt<\/strong> matches “file1.txt”, “file2.txt”, etc.<\/td>\n<\/tr>\n\n[ ] <\/strong><\/td>\nMatches any single character within the brackets. For instance, [aeiou] <\/strong>matches any vowel.<\/td>\n<\/tr>\n\nAnchors<\/strong><\/td>\n^<\/strong><\/td>\nMatches the beginning of a line or string. For example, ^hello<\/strong> matches lines that start with “hello”.<\/td>\n<\/tr>\n\n$ <\/strong><\/td>\nAnchors the regex at the end of the line. For instance, end$<\/strong> matches lines that end with \u201cend\u201d.<\/td>\n<\/tr>\n\nEscaping Character<\/strong><\/td>\n\/<\/strong><\/td>\n| Escapes the following character, treating it as a literal character instead of a metacharacter. For instance, \\* matches the asterisk character * literally.<\/td>\n<\/tr>\n | \nQuantifiers<\/strong><\/td>\n+ <\/strong><\/td>\n| Matcher one or more occurrences of the preceding character.<\/td>\n<\/tr>\n | \n{}<\/strong><\/td>\n| Specifies the exact number of occurrences or a range. For example, a{2} matches “aa”, and a{2,4} matches “aa”, “aaa”, or “aaaa”.<\/td>\n<\/tr>\n | \nNegation <\/strong><\/td>\n[^ ]<\/strong><\/td>\nNegates the character class, and matches any character not listed within the brackets. For instance, [^0-9]<\/strong> matches any character without a digit.<\/strong><\/td>\n<\/tr>\n\nGrouping<\/strong><\/td>\n()<\/strong><\/td>\nGroups pattern together and allow quantifiers to apply to the entire group. For example, (abc)+<\/strong> matches\u00a0 “abc”, “abcabc”, etc.<\/td>\n<\/tr>\n\nAlternation<\/strong><\/td>\n|<\/strong><\/td>\nRepresents alternation, allowing the matching of one pattern or another. For instance, cat|dog<\/strong> matches either “cat” or “dog”.<\/td>\n<\/tr>\n\nSpecial Characters<\/strong><\/td>\n. <\/strong><\/td>\n| Matches any single character except newline. For example, a.b matches “aab”, “acb”, etc., but not “a\\nb”.<\/td>\n<\/tr>\n | \nSequence for Common Characters<\/strong><\/td>\n\\w<\/strong><\/td>\n| Matches any word character both alphanumeric character and underscore.<\/td>\n<\/tr>\n | \n\\W<\/strong><\/td>\n| Matches any non-word characters except alphanumeric characters and underscore.<\/td>\n<\/tr>\n | \n\\d<\/strong><\/td>\n| Matches any digit.<\/td>\n<\/tr>\n | \n\\D<\/strong><\/td>\n| Matches any non-digit character.<\/td>\n<\/tr>\n | \n\\s<\/strong><\/td>\n| Matches any whitespace character.<\/td>\n<\/tr>\n | \n\\S<\/strong><\/td>\nMatches any non-whitespace character.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/span>How to Use Regex in Bash?<\/span><\/h2>\nIn Bash, Regex can be used in multiple ways for operations like finding a file extension, matching substring, and finding patterns without<\/strong> the original string. Bash provides several built-in utilities for regex, such as grep<\/strong>, sed<\/strong>, and awk<\/strong>. Here’s how you can use regex with these utilities:<\/p>\n<\/span>1. Using Regex Inside an If Clause<\/span><\/h3>\nIn Bash, regex within an if statement can be used for finding or matching tasks. For example, to check the extension of the file name, you can use regex<\/strong> within an if statement <\/strong>as below:<\/p>\n#!\/bin\/bash\n\nfilename="filex.txt"\n\nif [[ "$filename" =~ \\.txt$ ]]; then\n echo "Filename has a .txt extension"\nelse\n echo "Filename does not have a .txt extension"\nfi<\/code><\/pre>\nEXPLANATION<\/div> The script checks whether the filename stored in the variable filename<\/strong> ends with .txt <\/strong>extension. It uses a conditional statement with the =~<\/code> operator, which is used for pattern matching with regular expressions. The expression \\.txt$<\/code> matches the filename ends with .txt <\/code>extension. The sign $<\/code> anchors the pattern to the end of the string. <\/div><\/div>\n![\"Using](\"https:\/\/linuxsimply.com\/wp-content\/uploads\/2024\/03\/1.-regex-1.png\") The script output shows the result after matching the pattern (.txt) with the file extension.<\/p>\n
Note: <\/strong>You can check the article \u201c
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |