how to let part of the regex (that is variable) be matched literally, ignoring control characters? The Next CEO of Stack OverflowHow to do a regex search in a UTF-16LE file while in a UTF-8 locale?How do I keep a part of the pattern matched and use it to replace on BSD sed?How to delete the slash using REGEXScript that removes undesired characters from variablehow to use a variable in regex brace in awk?How do I replace multiple lines near regex characters?Control characters in a terminal with an active foreground processHow to change a variable that is part of the value of another variableHow does storing the regular expression in a shell variable avoid problems with quoting characters that are special to the shell?Capture only the numeric part with sed regex

Is French Guiana a (hard) EU border?

Is micro rebar a better way to reinforce concrete than rebar?

Grabbing quick drinks

Calculator final project in Python

Is there a way to save my career from absolute disaster?

How to write a definition with variants?

0-rank tensor vs vector in 1D

Would a grinding machine be a simple and workable propulsion system for an interplanetary spacecraft?

Would a completely good Muggle be able to use a wand?

RigExpert AA-35 - Interpreting The Information

How many extra stops do monopods offer for tele photographs?

Why does standard notation not preserve intervals (visually)

Is it possible to use a NPN BJT as switch, from single power source?

Find non-case sensitive string in a mixed list of elements?

Legal workarounds for testamentary trust perceived as unfair

Can MTA send mail via a relay without being told so?

Bartok - Syncopation (1): Meaning of notes in between Grand Staff

Is it professional to write unrelated content in an almost-empty email?

What is meant by "large scale tonal organization?"

What steps are necessary to read a Modern SSD in Medieval Europe?

Is it convenient to ask the journal's editor for two additional days to complete a review?

Necessary condition on homology group for a set to be contractible

Why isn't the Mueller report being released completely and unredacted?

What does "Its cash flow is deeply negative" mean?



how to let part of the regex (that is variable) be matched literally, ignoring control characters?



The Next CEO of Stack OverflowHow to do a regex search in a UTF-16LE file while in a UTF-8 locale?How do I keep a part of the pattern matched and use it to replace on BSD sed?How to delete the slash using REGEXScript that removes undesired characters from variablehow to use a variable in regex brace in awk?How do I replace multiple lines near regex characters?Control characters in a terminal with an active foreground processHow to change a variable that is part of the value of another variableHow does storing the regular expression in a shell variable avoid problems with quoting characters that are special to the shell?Capture only the numeric part with sed regex










0















I got some filenames containing characters that are regex special control ones.



I need to prepare a regex that considers all these characters literally.



Simplified test case:



strFilenameOnDB="some ( file ) name +.ok";
strFilenameToCheck="$strFilenameOnDB"; #code simplification
strRegex=".*$strFilenameToCheck.*";
if [[ "$strFilenameOnDB" =~ $strRegex ]];then echo OK;fi


the above will (of course) fail.



in perl we can use /Q /E (https://stackoverflow.com/a/3971923/1422630) to turn the expanded $strRegex into literal, is there anything like that for bash?



Obs.: I will post what I am already doing, but I wonder if there is a better way?










share|improve this question






















  • If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

    – Kusalananda
    yesterday















0















I got some filenames containing characters that are regex special control ones.



I need to prepare a regex that considers all these characters literally.



Simplified test case:



strFilenameOnDB="some ( file ) name +.ok";
strFilenameToCheck="$strFilenameOnDB"; #code simplification
strRegex=".*$strFilenameToCheck.*";
if [[ "$strFilenameOnDB" =~ $strRegex ]];then echo OK;fi


the above will (of course) fail.



in perl we can use /Q /E (https://stackoverflow.com/a/3971923/1422630) to turn the expanded $strRegex into literal, is there anything like that for bash?



Obs.: I will post what I am already doing, but I wonder if there is a better way?










share|improve this question






















  • If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

    – Kusalananda
    yesterday













0












0








0








I got some filenames containing characters that are regex special control ones.



I need to prepare a regex that considers all these characters literally.



Simplified test case:



strFilenameOnDB="some ( file ) name +.ok";
strFilenameToCheck="$strFilenameOnDB"; #code simplification
strRegex=".*$strFilenameToCheck.*";
if [[ "$strFilenameOnDB" =~ $strRegex ]];then echo OK;fi


the above will (of course) fail.



in perl we can use /Q /E (https://stackoverflow.com/a/3971923/1422630) to turn the expanded $strRegex into literal, is there anything like that for bash?



Obs.: I will post what I am already doing, but I wonder if there is a better way?










share|improve this question














I got some filenames containing characters that are regex special control ones.



I need to prepare a regex that considers all these characters literally.



Simplified test case:



strFilenameOnDB="some ( file ) name +.ok";
strFilenameToCheck="$strFilenameOnDB"; #code simplification
strRegex=".*$strFilenameToCheck.*";
if [[ "$strFilenameOnDB" =~ $strRegex ]];then echo OK;fi


the above will (of course) fail.



in perl we can use /Q /E (https://stackoverflow.com/a/3971923/1422630) to turn the expanded $strRegex into literal, is there anything like that for bash?



Obs.: I will post what I am already doing, but I wonder if there is a better way?







bash regular-expression






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 days ago









Aquarius PowerAquarius Power

1,77732139




1,77732139












  • If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

    – Kusalananda
    yesterday

















  • If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

    – Kusalananda
    yesterday
















If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

– Kusalananda
yesterday





If all you want to do is to check for the occurrence of one string in another, then your question is a duplicate of Test if a string contains a substring

– Kusalananda
yesterday










4 Answers
4






active

oldest

votes


















2














In Bash’s =~ match operator, literal strings in the regex can be specified by putting them within double-quotes.



So in theory you’d just need to turn Perl’s Q and E into one double-quote each.



But, however, if your requirement is to use a regex that is partly variable (ie contains other shell variables to be expanded) and partly literal, and that is itself contained in a shell variable, then I’m afraid the only way out is to also use eval.



That is, your example code would become like this:



strFilenameOnDB="some ( file ) name +.ok";
strFilenameToCheck="$strFilenameOnDB"; #code simplification
strRegex=".*"$strFilenameToCheck".*"; # <<--- note the backslash before each _inner_ double-quote: this is Bash’s syntax to embed a literal double-quote in a string _made by_ double-quotes

# then we shall use eval on the whole test operation

if eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]';then echo OK;fi

# or, using a fine Bash’s shortcut:

eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]' && echo OK


To sum it up, in order to embed literal strings in a partly variable regex contained in a shell variable, you need to:



  1. use " and another " in place of Perl’s Q and E

  2. embed the whole test command inside a carefully quoted eval

All this is required in order to expand the string containing the regex first, so that the two " in the shell variable are considered as start-end of literal part of the regex rather than as the usual Bash’s quoting characters, and then the entire match operation is executed on such resulting pattern.



(A well harder task comes when you have to include double-quotes or backslashes within a regex within a double-quoted shell variable..)



As a side-note, you don’t actually need the .* at beginning and end of a regex because those are usually implied in Bash’s regex operation. In fact you rather need to explicitly specify start-end anchors (^ and $) when you don’t want to imply other characters before and after a regex.






share|improve this answer

























  • this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

    – Aquarius Power
    2 days ago







  • 1





    Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

    – LL3
    2 days ago











  • cool thx again!

    – Aquarius Power
    2 days ago


















2














Are you just looking to see if the filename contains a particular substring? Because if you do that with [[ =~ ]], you don't need the leading and trailing .* parts: the regex match is more like a search, it's enough for a match to be found anywhere in the string.



Also, in Bash, quoting (parts of) the pattern (or a variable containing the pattern) removes the special meanings of the quoted characters. So, e.g. this would match:



re=' + '
[[ "foo + doo" =~ "$re" ]] && echo match


while this doesn't (the plus is special now and doesn't match itself):



re=' + '
[[ "foo + doo" =~ $re ]] && echo match


In comparison, a non-regex match will require matching against the whole string, so you need a leading and a trailing *:



pattern=' * '
[[ "foo * doo" = *"$pattern"* ]] && echo match





share|improve this answer






























    2














    Personally, I would not combine the string that you'd like to be literal with the regular expression bits that you'd like to be interpreted as regular expression pattern. The literal string bit of the expression should be double quoted, the bits that needs to be interpreted as a regular expression should not be.



    [[ $strFilenameOnDB =~ .*"$strFilenameToCheck".* ]] && echo OK


    In this case though, since regular expressions aren't by default anchored to the start or end of the string (unlike filename globbing patterns that are always matching a complete string), you could do without the flanking .* completely.






    share|improve this answer

























    • very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

      – Aquarius Power
      2 days ago


















    0














    I change the matcher this way:



    sedExact='s"(.)"[1]"g';
    strRegex=".*$(echo "$strFilenameToCheck" |sed -r "$sedExact").*";





    share|improve this answer























      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509312%2fhow-to-let-part-of-the-regex-that-is-variable-be-matched-literally-ignoring-c%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      In Bash’s =~ match operator, literal strings in the regex can be specified by putting them within double-quotes.



      So in theory you’d just need to turn Perl’s Q and E into one double-quote each.



      But, however, if your requirement is to use a regex that is partly variable (ie contains other shell variables to be expanded) and partly literal, and that is itself contained in a shell variable, then I’m afraid the only way out is to also use eval.



      That is, your example code would become like this:



      strFilenameOnDB="some ( file ) name +.ok";
      strFilenameToCheck="$strFilenameOnDB"; #code simplification
      strRegex=".*"$strFilenameToCheck".*"; # <<--- note the backslash before each _inner_ double-quote: this is Bash’s syntax to embed a literal double-quote in a string _made by_ double-quotes

      # then we shall use eval on the whole test operation

      if eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]';then echo OK;fi

      # or, using a fine Bash’s shortcut:

      eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]' && echo OK


      To sum it up, in order to embed literal strings in a partly variable regex contained in a shell variable, you need to:



      1. use " and another " in place of Perl’s Q and E

      2. embed the whole test command inside a carefully quoted eval

      All this is required in order to expand the string containing the regex first, so that the two " in the shell variable are considered as start-end of literal part of the regex rather than as the usual Bash’s quoting characters, and then the entire match operation is executed on such resulting pattern.



      (A well harder task comes when you have to include double-quotes or backslashes within a regex within a double-quoted shell variable..)



      As a side-note, you don’t actually need the .* at beginning and end of a regex because those are usually implied in Bash’s regex operation. In fact you rather need to explicitly specify start-end anchors (^ and $) when you don’t want to imply other characters before and after a regex.






      share|improve this answer

























      • this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

        – Aquarius Power
        2 days ago







      • 1





        Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

        – LL3
        2 days ago











      • cool thx again!

        – Aquarius Power
        2 days ago















      2














      In Bash’s =~ match operator, literal strings in the regex can be specified by putting them within double-quotes.



      So in theory you’d just need to turn Perl’s Q and E into one double-quote each.



      But, however, if your requirement is to use a regex that is partly variable (ie contains other shell variables to be expanded) and partly literal, and that is itself contained in a shell variable, then I’m afraid the only way out is to also use eval.



      That is, your example code would become like this:



      strFilenameOnDB="some ( file ) name +.ok";
      strFilenameToCheck="$strFilenameOnDB"; #code simplification
      strRegex=".*"$strFilenameToCheck".*"; # <<--- note the backslash before each _inner_ double-quote: this is Bash’s syntax to embed a literal double-quote in a string _made by_ double-quotes

      # then we shall use eval on the whole test operation

      if eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]';then echo OK;fi

      # or, using a fine Bash’s shortcut:

      eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]' && echo OK


      To sum it up, in order to embed literal strings in a partly variable regex contained in a shell variable, you need to:



      1. use " and another " in place of Perl’s Q and E

      2. embed the whole test command inside a carefully quoted eval

      All this is required in order to expand the string containing the regex first, so that the two " in the shell variable are considered as start-end of literal part of the regex rather than as the usual Bash’s quoting characters, and then the entire match operation is executed on such resulting pattern.



      (A well harder task comes when you have to include double-quotes or backslashes within a regex within a double-quoted shell variable..)



      As a side-note, you don’t actually need the .* at beginning and end of a regex because those are usually implied in Bash’s regex operation. In fact you rather need to explicitly specify start-end anchors (^ and $) when you don’t want to imply other characters before and after a regex.






      share|improve this answer

























      • this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

        – Aquarius Power
        2 days ago







      • 1





        Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

        – LL3
        2 days ago











      • cool thx again!

        – Aquarius Power
        2 days ago













      2












      2








      2







      In Bash’s =~ match operator, literal strings in the regex can be specified by putting them within double-quotes.



      So in theory you’d just need to turn Perl’s Q and E into one double-quote each.



      But, however, if your requirement is to use a regex that is partly variable (ie contains other shell variables to be expanded) and partly literal, and that is itself contained in a shell variable, then I’m afraid the only way out is to also use eval.



      That is, your example code would become like this:



      strFilenameOnDB="some ( file ) name +.ok";
      strFilenameToCheck="$strFilenameOnDB"; #code simplification
      strRegex=".*"$strFilenameToCheck".*"; # <<--- note the backslash before each _inner_ double-quote: this is Bash’s syntax to embed a literal double-quote in a string _made by_ double-quotes

      # then we shall use eval on the whole test operation

      if eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]';then echo OK;fi

      # or, using a fine Bash’s shortcut:

      eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]' && echo OK


      To sum it up, in order to embed literal strings in a partly variable regex contained in a shell variable, you need to:



      1. use " and another " in place of Perl’s Q and E

      2. embed the whole test command inside a carefully quoted eval

      All this is required in order to expand the string containing the regex first, so that the two " in the shell variable are considered as start-end of literal part of the regex rather than as the usual Bash’s quoting characters, and then the entire match operation is executed on such resulting pattern.



      (A well harder task comes when you have to include double-quotes or backslashes within a regex within a double-quoted shell variable..)



      As a side-note, you don’t actually need the .* at beginning and end of a regex because those are usually implied in Bash’s regex operation. In fact you rather need to explicitly specify start-end anchors (^ and $) when you don’t want to imply other characters before and after a regex.






      share|improve this answer















      In Bash’s =~ match operator, literal strings in the regex can be specified by putting them within double-quotes.



      So in theory you’d just need to turn Perl’s Q and E into one double-quote each.



      But, however, if your requirement is to use a regex that is partly variable (ie contains other shell variables to be expanded) and partly literal, and that is itself contained in a shell variable, then I’m afraid the only way out is to also use eval.



      That is, your example code would become like this:



      strFilenameOnDB="some ( file ) name +.ok";
      strFilenameToCheck="$strFilenameOnDB"; #code simplification
      strRegex=".*"$strFilenameToCheck".*"; # <<--- note the backslash before each _inner_ double-quote: this is Bash’s syntax to embed a literal double-quote in a string _made by_ double-quotes

      # then we shall use eval on the whole test operation

      if eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]';then echo OK;fi

      # or, using a fine Bash’s shortcut:

      eval '[[ "$strFilenameOnDB" =~ '"$strRegex"' ]]' && echo OK


      To sum it up, in order to embed literal strings in a partly variable regex contained in a shell variable, you need to:



      1. use " and another " in place of Perl’s Q and E

      2. embed the whole test command inside a carefully quoted eval

      All this is required in order to expand the string containing the regex first, so that the two " in the shell variable are considered as start-end of literal part of the regex rather than as the usual Bash’s quoting characters, and then the entire match operation is executed on such resulting pattern.



      (A well harder task comes when you have to include double-quotes or backslashes within a regex within a double-quoted shell variable..)



      As a side-note, you don’t actually need the .* at beginning and end of a regex because those are usually implied in Bash’s regex operation. In fact you rather need to explicitly specify start-end anchors (^ and $) when you don’t want to imply other characters before and after a regex.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited 2 days ago

























      answered 2 days ago









      LL3LL3

      3315




      3315












      • this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

        – Aquarius Power
        2 days ago







      • 1





        Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

        – LL3
        2 days ago











      • cool thx again!

        – Aquarius Power
        2 days ago

















      • this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

        – Aquarius Power
        2 days ago







      • 1





        Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

        – LL3
        2 days ago











      • cool thx again!

        – Aquarius Power
        2 days ago
















      this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

      – Aquarius Power
      2 days ago






      this worked on the terminal test case: strRegex=".*"$strFilenameToCheck".*". But when the if is inside a function, only the eval tip worked, thx! :)

      – Aquarius Power
      2 days ago





      1




      1





      Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

      – LL3
      2 days ago





      Ok, however I just noticed a typo I made when I first edited the answer..: please surround with double-quotes the $strRegex in the eval, otherwise in case of glob chars like * ? [ ] ( ) alone (ie with spaces around) they would be interpreted by the shell as file name expansion thus listing matching file names present in current directory.

      – LL3
      2 days ago













      cool thx again!

      – Aquarius Power
      2 days ago





      cool thx again!

      – Aquarius Power
      2 days ago













      2














      Are you just looking to see if the filename contains a particular substring? Because if you do that with [[ =~ ]], you don't need the leading and trailing .* parts: the regex match is more like a search, it's enough for a match to be found anywhere in the string.



      Also, in Bash, quoting (parts of) the pattern (or a variable containing the pattern) removes the special meanings of the quoted characters. So, e.g. this would match:



      re=' + '
      [[ "foo + doo" =~ "$re" ]] && echo match


      while this doesn't (the plus is special now and doesn't match itself):



      re=' + '
      [[ "foo + doo" =~ $re ]] && echo match


      In comparison, a non-regex match will require matching against the whole string, so you need a leading and a trailing *:



      pattern=' * '
      [[ "foo * doo" = *"$pattern"* ]] && echo match





      share|improve this answer



























        2














        Are you just looking to see if the filename contains a particular substring? Because if you do that with [[ =~ ]], you don't need the leading and trailing .* parts: the regex match is more like a search, it's enough for a match to be found anywhere in the string.



        Also, in Bash, quoting (parts of) the pattern (or a variable containing the pattern) removes the special meanings of the quoted characters. So, e.g. this would match:



        re=' + '
        [[ "foo + doo" =~ "$re" ]] && echo match


        while this doesn't (the plus is special now and doesn't match itself):



        re=' + '
        [[ "foo + doo" =~ $re ]] && echo match


        In comparison, a non-regex match will require matching against the whole string, so you need a leading and a trailing *:



        pattern=' * '
        [[ "foo * doo" = *"$pattern"* ]] && echo match





        share|improve this answer

























          2












          2








          2







          Are you just looking to see if the filename contains a particular substring? Because if you do that with [[ =~ ]], you don't need the leading and trailing .* parts: the regex match is more like a search, it's enough for a match to be found anywhere in the string.



          Also, in Bash, quoting (parts of) the pattern (or a variable containing the pattern) removes the special meanings of the quoted characters. So, e.g. this would match:



          re=' + '
          [[ "foo + doo" =~ "$re" ]] && echo match


          while this doesn't (the plus is special now and doesn't match itself):



          re=' + '
          [[ "foo + doo" =~ $re ]] && echo match


          In comparison, a non-regex match will require matching against the whole string, so you need a leading and a trailing *:



          pattern=' * '
          [[ "foo * doo" = *"$pattern"* ]] && echo match





          share|improve this answer













          Are you just looking to see if the filename contains a particular substring? Because if you do that with [[ =~ ]], you don't need the leading and trailing .* parts: the regex match is more like a search, it's enough for a match to be found anywhere in the string.



          Also, in Bash, quoting (parts of) the pattern (or a variable containing the pattern) removes the special meanings of the quoted characters. So, e.g. this would match:



          re=' + '
          [[ "foo + doo" =~ "$re" ]] && echo match


          while this doesn't (the plus is special now and doesn't match itself):



          re=' + '
          [[ "foo + doo" =~ $re ]] && echo match


          In comparison, a non-regex match will require matching against the whole string, so you need a leading and a trailing *:



          pattern=' * '
          [[ "foo * doo" = *"$pattern"* ]] && echo match






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          ilkkachuilkkachu

          62.8k10103180




          62.8k10103180





















              2














              Personally, I would not combine the string that you'd like to be literal with the regular expression bits that you'd like to be interpreted as regular expression pattern. The literal string bit of the expression should be double quoted, the bits that needs to be interpreted as a regular expression should not be.



              [[ $strFilenameOnDB =~ .*"$strFilenameToCheck".* ]] && echo OK


              In this case though, since regular expressions aren't by default anchored to the start or end of the string (unlike filename globbing patterns that are always matching a complete string), you could do without the flanking .* completely.






              share|improve this answer

























              • very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

                – Aquarius Power
                2 days ago















              2














              Personally, I would not combine the string that you'd like to be literal with the regular expression bits that you'd like to be interpreted as regular expression pattern. The literal string bit of the expression should be double quoted, the bits that needs to be interpreted as a regular expression should not be.



              [[ $strFilenameOnDB =~ .*"$strFilenameToCheck".* ]] && echo OK


              In this case though, since regular expressions aren't by default anchored to the start or end of the string (unlike filename globbing patterns that are always matching a complete string), you could do without the flanking .* completely.






              share|improve this answer

























              • very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

                – Aquarius Power
                2 days ago













              2












              2








              2







              Personally, I would not combine the string that you'd like to be literal with the regular expression bits that you'd like to be interpreted as regular expression pattern. The literal string bit of the expression should be double quoted, the bits that needs to be interpreted as a regular expression should not be.



              [[ $strFilenameOnDB =~ .*"$strFilenameToCheck".* ]] && echo OK


              In this case though, since regular expressions aren't by default anchored to the start or end of the string (unlike filename globbing patterns that are always matching a complete string), you could do without the flanking .* completely.






              share|improve this answer















              Personally, I would not combine the string that you'd like to be literal with the regular expression bits that you'd like to be interpreted as regular expression pattern. The literal string bit of the expression should be double quoted, the bits that needs to be interpreted as a regular expression should not be.



              [[ $strFilenameOnDB =~ .*"$strFilenameToCheck".* ]] && echo OK


              In this case though, since regular expressions aren't by default anchored to the start or end of the string (unlike filename globbing patterns that are always matching a complete string), you could do without the flanking .* completely.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 2 days ago

























              answered 2 days ago









              KusalanandaKusalananda

              138k17258428




              138k17258428












              • very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

                – Aquarius Power
                2 days ago

















              • very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

                – Aquarius Power
                2 days ago
















              very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

              – Aquarius Power
              2 days ago





              very interesting thx! but the regex is actually a parameter and comes from outside the function (that would be only the if line here).

              – Aquarius Power
              2 days ago











              0














              I change the matcher this way:



              sedExact='s"(.)"[1]"g';
              strRegex=".*$(echo "$strFilenameToCheck" |sed -r "$sedExact").*";





              share|improve this answer



























                0














                I change the matcher this way:



                sedExact='s"(.)"[1]"g';
                strRegex=".*$(echo "$strFilenameToCheck" |sed -r "$sedExact").*";





                share|improve this answer

























                  0












                  0








                  0







                  I change the matcher this way:



                  sedExact='s"(.)"[1]"g';
                  strRegex=".*$(echo "$strFilenameToCheck" |sed -r "$sedExact").*";





                  share|improve this answer













                  I change the matcher this way:



                  sedExact='s"(.)"[1]"g';
                  strRegex=".*$(echo "$strFilenameToCheck" |sed -r "$sedExact").*";






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 days ago









                  Aquarius PowerAquarius Power

                  1,77732139




                  1,77732139



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509312%2fhow-to-let-part-of-the-regex-that-is-variable-be-matched-literally-ignoring-c%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      getting Checkpoint VPN SSL Network Extender working in the command lineHow to connect to CheckPoint VPN on Ubuntu 18.04LTS?Will the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayVPN SSL Network Extender in FirefoxLinux Checkpoint SNX tool configuration issuesCheck Point - Connect under Linux - snx + OTPSNX VPN Ububuntu 18.XXUsing Checkpoint VPN SSL Network Extender CLI with certificateVPN with network manager (nm-applet) is not workingWill the Linux ( red-hat ) Open VPNC Client connect to checkpoint or nortel VPN gateways?VPN client for linux machine + support checkpoint gatewayImport VPN config files to NetworkManager from command lineTrouble connecting to VPN using network-manager, while command line worksStart a VPN connection with PPTP protocol on command linestarting a docker service daemon breaks the vpn networkCan't connect to vpn with Network-managerVPN SSL Network Extender in FirefoxUsing Checkpoint VPN SSL Network Extender CLI with certificate

                      NetworkManager fails with “Could not find source connection”Trouble connecting to VPN using network-manager, while command line worksHow can I be notified about state changes to a VPN adapterBacktrack 5 R3 - Refuses to connect to VPNFeed all traffic through OpenVPN for a specific network namespace onlyRun daemon on startup in Debian once openvpn connection establishedpfsense tcp connection between openvpn and lan is brokenInternet connection problem with web browsers onlyWhy does NetworkManager explicitly support tun/tap devices?Browser issues with VPNTwo IP addresses assigned to the same network card - OpenVPN issues?Cannot connect to WiFi with nmcli, although secrets are provided

                      대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495