Skip to main content

How to use regex in Linux Bash

Regex or regular expression uses a pattern that is compared to a string and will check if the pattern exists or the string matches the pattern.

In Bash script a simple if then else and a regex pattern can be used to check if the pattern matches a set of input on a text file.

Bash script below is a simple example on how to use regex in Bash using if then else.

Script below uses this sample file "number_file.txt" with the sample text or contents shown below.

a12567

b23567

c34568

12w678

23908

35107

23469

x1234

y3432

12094x

123y8

====

#!/bin/sh

patx="^[0-9]+$"

while IFS= read -r line; do

    echo "Text read from file: $line"

    if [[ $line =~ $patx  ]]

               then

                 echo "Hey this one is alpahumeric --> $line."

     else

                 echo "Hey this one is a group of numbers --> $line."

     fi

done < number_file.txt

===

Above Bash script will check the number_file.txt,  each output line will be checked if it is  numbers only or has numbers and letters on it.

The operator used in Bash if then else to use regex is “=~” it’s the equal sign and the tilde character.

The script will read the file line by line, and compare the line to the regex pattern.

Regex pattern use: patx="^[0-9]+$"


Bash script below is another implementation but uses the built-in type.

===

#!/bin/sh

while IFS= read -r line; do

    echo "Text read from file: $line"

    if [[ $line =~ [^[:digit:]]  ]]

               then                        

                 echo "Hey this is alphanumeric --> $line."

     else

                 echo "Hey this is a group of numbers --> $line."

     fi

done < number_file.txt

===

Regex pattern use: [^[:digit:]]

:digit: built-in type in Bash.

Sample output of the Bash script:


That’s just a simple illustration on how to use regex in Bash script, this will be useful if the input follows a pattern or the requirements is quite simple such as to check if the string has letters or just numbers.


Till next time. Stay safe! and keep things up! 

Do ASAP, Always Say A Prayer...

================================

Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:

https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

Heaven's Dew Fall  Prayer app for Android :

https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer

Catholic Rosary Guide  for Android:

Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully. 

https://play.google.com/store/apps/details?id=com.myrosaryapp

Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:

https://play.google.com/store/apps/details?id=com.dmercyapp 

Comments

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...

Delete Directories with Wildcards using rd or rmdir

  Deleting files in command prompt using wildcards is quite straight forward. Command below will delete all text (".txt") files on the specified path.      Del D:\txtlog\*.txt Command above will delete all files with ".txt" extension in d:\txtlog directory. Easy enough to delete all matching files. Using the same method with rmdir or rd command this will not work. For example, if we have a directory on d drive that is auto-generated by an application and the filename is consistent with a pattern plus incrementing number at the end to differentiate the folder from other folders.    D:\baklogs\log1\    D:\baklogs\log2\    D:\baklogs\log3\    Etc..    D:\baklogs\log100\ The folder name has a consistent pattern that is preceded by the word “log” plus incrementing number. If the command below is executed to remove the directories in one go, an error is shown which h...