Pass shell variable as a /pattern/ to awk2019 Community Moderator ElectionHow to pass shell variable to an awk search pattern?How to use a variable inside an awk statement?make awk print the line that match a variable and the next n lines and use a variable in awkAWK and Bash Scriptingusing awk with variablesPass Shell variable to awkawk search for string containing forward slash in variablePass a variable in another variable within an awkhow to use variable with awkHow to make variable be taken into accountGawk: Passing arrays to functionsHow can I convert this bash function to the fish shellBEGIN and END with the awk commandBest way to iterate through the following awk commandHow to pass shell variable to an awk search pattern?(Shell Script) Variable not pass correctly when fetching value from file?Use awk interactively through a pipePass Shell variable to awkusing awk with variablesDeclaring a variable that does not have input

Does Doodling or Improvising on the Piano Have Any Benefits?

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

Picking the different solutions to the time independent Schrodinger eqaution

Redundant comparison & "if" before assignment

What should you do when eye contact makes your subordinate uncomfortable?

How does the math work for Perception checks?

15% tax on $7.5k earnings. Is that right?

Has any country ever had 2 former presidents in jail simultaneously?

Hero deduces identity of a killer

Fear of getting stuck on one programming language / technology that is not used in my country

Why is the "ls" command showing permissions of files in a FAT32 partition?

What is Cash Advance APR?

Mixing PEX brands

Why does the Sun have different day lengths, but not the gas giants?

Store Credit Card Information in Password Manager?

putting logo on same line but after title, latex

Why is so much work done on numerical verification of the Riemann Hypothesis?

Multiplicative persistence

Using substitution ciphers to generate new alphabets in a novel

Does the Linux kernel need a file system to run?

Yosemite Fire Rings - What to Expect?

Electoral considerations aside, what are potential benefits, for the US, of policy changes proposed by the tweet recognizing Golan annexation?

Why is this estimator biased?

Does IPv6 have similar concept of network mask?



Pass shell variable as a /pattern/ to awk



2019 Community Moderator ElectionHow to pass shell variable to an awk search pattern?How to use a variable inside an awk statement?make awk print the line that match a variable and the next n lines and use a variable in awkAWK and Bash Scriptingusing awk with variablesPass Shell variable to awkawk search for string containing forward slash in variablePass a variable in another variable within an awkhow to use variable with awkHow to make variable be taken into accountGawk: Passing arrays to functionsHow can I convert this bash function to the fish shellBEGIN and END with the awk commandBest way to iterate through the following awk commandHow to pass shell variable to an awk search pattern?(Shell Script) Variable not pass correctly when fetching value from file?Use awk interactively through a pipePass Shell variable to awkusing awk with variablesDeclaring a variable that does not have input










55















Having the following in one of my shell functions:



function _process () 
awk -v l="$line" '
BEGIN p=0
/'"$1"'/ p=1
END if(p) print l >> "outfile.txt"
'



, so when called as _process $arg, $arg gets passed as $1, and used as a search pattern. It works this way, because shell expands $1 in place of awk pattern! Also l can be used inside awk program, being declared with -v l="$line". All fine.



Is it possible in same manner give pattern to search as a variable?



Following will not work,



awk -v l="$line" -v search="$pattern" '
BEGIN p=0
/search/ p=1
END if(p) print l >> "outfile.txt"
'


,as awk will not interpret /search/ as a variable, but instead literally.










share|improve this question




























    55















    Having the following in one of my shell functions:



    function _process () 
    awk -v l="$line" '
    BEGIN p=0
    /'"$1"'/ p=1
    END if(p) print l >> "outfile.txt"
    '



    , so when called as _process $arg, $arg gets passed as $1, and used as a search pattern. It works this way, because shell expands $1 in place of awk pattern! Also l can be used inside awk program, being declared with -v l="$line". All fine.



    Is it possible in same manner give pattern to search as a variable?



    Following will not work,



    awk -v l="$line" -v search="$pattern" '
    BEGIN p=0
    /search/ p=1
    END if(p) print l >> "outfile.txt"
    '


    ,as awk will not interpret /search/ as a variable, but instead literally.










    share|improve this question


























      55












      55








      55


      7






      Having the following in one of my shell functions:



      function _process () 
      awk -v l="$line" '
      BEGIN p=0
      /'"$1"'/ p=1
      END if(p) print l >> "outfile.txt"
      '



      , so when called as _process $arg, $arg gets passed as $1, and used as a search pattern. It works this way, because shell expands $1 in place of awk pattern! Also l can be used inside awk program, being declared with -v l="$line". All fine.



      Is it possible in same manner give pattern to search as a variable?



      Following will not work,



      awk -v l="$line" -v search="$pattern" '
      BEGIN p=0
      /search/ p=1
      END if(p) print l >> "outfile.txt"
      '


      ,as awk will not interpret /search/ as a variable, but instead literally.










      share|improve this question
















      Having the following in one of my shell functions:



      function _process () 
      awk -v l="$line" '
      BEGIN p=0
      /'"$1"'/ p=1
      END if(p) print l >> "outfile.txt"
      '



      , so when called as _process $arg, $arg gets passed as $1, and used as a search pattern. It works this way, because shell expands $1 in place of awk pattern! Also l can be used inside awk program, being declared with -v l="$line". All fine.



      Is it possible in same manner give pattern to search as a variable?



      Following will not work,



      awk -v l="$line" -v search="$pattern" '
      BEGIN p=0
      /search/ p=1
      END if(p) print l >> "outfile.txt"
      '


      ,as awk will not interpret /search/ as a variable, but instead literally.







      shell awk quoting variable






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 21 '14 at 23:04









      Gilles

      543k12811011618




      543k12811011618










      asked Mar 21 '14 at 15:03









      branquitobranquito

      4451616




      4451616




















          5 Answers
          5






          active

          oldest

          votes


















          43














          Use awk's ~ operator, and you don't need to provide a literal regex on the right-hand side:



          function _process () 
          awk -v l="$line" -v pattern="$1" '
          $0 ~ pattern p=1
          END if(p) print l >> "outfile.txt"
          '



          Although this would be more efficient (don't have to read the whole file)



          function _process () 
          grep -q "$1" && echo "$line"



          Depending on the pattern, may want grep -Eq "$1"






          share|improve this answer























          • This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

            – branquito
            Mar 21 '14 at 15:30






          • 1





            I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

            – glenn jackman
            Mar 21 '14 at 15:35











          • yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

            – branquito
            Mar 21 '14 at 15:42











          • maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

            – branquito
            Mar 21 '14 at 15:53











          • Please show the contents of $line -- do it in your question for proper formatting.

            – glenn jackman
            Mar 21 '14 at 15:57


















          16














          awk -v pattern="$1" '$0 ~ pattern'


          Has an issue in that awk expands the ANSI C escape sequences (like n for newline, f for form feed, \ for backslash and so on) in $1. So it becomes an issue if $1 contains backslash characters which is common in regular expressions. Another approach that doesn't suffer from that issue is to write it:



          PATTERN=$1 awk '$0 ~ ENVIRON["PATTERN"]'


          How bad it's going to be will depend on the awk implementation.



          $ nawk -v 'a=.' 'BEGIN print a'
          .
          $ mawk -v 'a=.' 'BEGIN print a'
          .
          $ gawk -v 'a=.' 'BEGIN print a'
          gawk: warning: escape sequence `.' treated as plain `.'
          .


          All awks work the same for valid escape sequences though:



          $ a='\-b' awk 'BEGIN print ENVIRON["a"]' | od -tc
          0000000 - b n
          0000006


          (content of $a passed as-is)



          $ awk -v a='\-b' 'BEGIN print a' | od -tc
          0000000 - b n
          0000004


          (\ changed to and b changed to a backspace character).






          share|improve this answer

























          • So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

            – branquito
            Mar 21 '14 at 16:24






          • 2





            for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

            – Stéphane Chazelas
            Mar 21 '14 at 16:30












          • it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

            – branquito
            Mar 21 '14 at 16:34







          • 1





            Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

            – Stéphane Chazelas
            Mar 21 '14 at 17:03






          • 1





            Because you need to export a shell variable for it to be passed in the environment to a command.

            – Stéphane Chazelas
            Mar 21 '14 at 17:20


















          5














          Try something like:



          awk -v l="$line" -v search="$pattern" 'BEGIN p=0; if ( match( $0, search )) p=1; END if(p) print l >> "outfile.txt" '





          share|improve this answer























          • If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

            – branquito
            Mar 21 '14 at 15:22






          • 1





            The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

            – Hunter Eidson
            Mar 21 '14 at 15:24


















          0














          No, but you can simply interpolate the pattern into the double-quoted string you pass to awk:



          awk -v l="$line" "BEGIN p=0; /$pattern/ p=1; END if(p) print l >> "outfile.txt" "


          Note that you now have to escape the double-quoted awk literal, but it is still the simplest way of accomplishing this.






          share|improve this answer























          • Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

            – branquito
            Mar 21 '14 at 15:14






          • 2





            Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

            – Kilian Foth
            Mar 21 '14 at 15:26






          • 4





            But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

            – Stéphane Chazelas
            Mar 21 '14 at 16:17











          • is that downside of this approach only, having all wrapped in "" ?

            – branquito
            Mar 21 '14 at 16:27


















          -3














          You could use the eval function which resolves in this example the nets variable before the awk is run.



          nets="searchtext"
          eval "awk '/"$nets"/'" file.txt





          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%2f120788%2fpass-shell-variable-as-a-pattern-to-awk%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            5 Answers
            5






            active

            oldest

            votes








            5 Answers
            5






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            43














            Use awk's ~ operator, and you don't need to provide a literal regex on the right-hand side:



            function _process () 
            awk -v l="$line" -v pattern="$1" '
            $0 ~ pattern p=1
            END if(p) print l >> "outfile.txt"
            '



            Although this would be more efficient (don't have to read the whole file)



            function _process () 
            grep -q "$1" && echo "$line"



            Depending on the pattern, may want grep -Eq "$1"






            share|improve this answer























            • This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

              – branquito
              Mar 21 '14 at 15:30






            • 1





              I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

              – glenn jackman
              Mar 21 '14 at 15:35











            • yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

              – branquito
              Mar 21 '14 at 15:42











            • maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

              – branquito
              Mar 21 '14 at 15:53











            • Please show the contents of $line -- do it in your question for proper formatting.

              – glenn jackman
              Mar 21 '14 at 15:57















            43














            Use awk's ~ operator, and you don't need to provide a literal regex on the right-hand side:



            function _process () 
            awk -v l="$line" -v pattern="$1" '
            $0 ~ pattern p=1
            END if(p) print l >> "outfile.txt"
            '



            Although this would be more efficient (don't have to read the whole file)



            function _process () 
            grep -q "$1" && echo "$line"



            Depending on the pattern, may want grep -Eq "$1"






            share|improve this answer























            • This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

              – branquito
              Mar 21 '14 at 15:30






            • 1





              I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

              – glenn jackman
              Mar 21 '14 at 15:35











            • yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

              – branquito
              Mar 21 '14 at 15:42











            • maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

              – branquito
              Mar 21 '14 at 15:53











            • Please show the contents of $line -- do it in your question for proper formatting.

              – glenn jackman
              Mar 21 '14 at 15:57













            43












            43








            43







            Use awk's ~ operator, and you don't need to provide a literal regex on the right-hand side:



            function _process () 
            awk -v l="$line" -v pattern="$1" '
            $0 ~ pattern p=1
            END if(p) print l >> "outfile.txt"
            '



            Although this would be more efficient (don't have to read the whole file)



            function _process () 
            grep -q "$1" && echo "$line"



            Depending on the pattern, may want grep -Eq "$1"






            share|improve this answer













            Use awk's ~ operator, and you don't need to provide a literal regex on the right-hand side:



            function _process () 
            awk -v l="$line" -v pattern="$1" '
            $0 ~ pattern p=1
            END if(p) print l >> "outfile.txt"
            '



            Although this would be more efficient (don't have to read the whole file)



            function _process () 
            grep -q "$1" && echo "$line"



            Depending on the pattern, may want grep -Eq "$1"







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 21 '14 at 15:16









            glenn jackmanglenn jackman

            52.6k573114




            52.6k573114












            • This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

              – branquito
              Mar 21 '14 at 15:30






            • 1





              I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

              – glenn jackman
              Mar 21 '14 at 15:35











            • yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

              – branquito
              Mar 21 '14 at 15:42











            • maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

              – branquito
              Mar 21 '14 at 15:53











            • Please show the contents of $line -- do it in your question for proper formatting.

              – glenn jackman
              Mar 21 '14 at 15:57

















            • This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

              – branquito
              Mar 21 '14 at 15:30






            • 1





              I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

              – glenn jackman
              Mar 21 '14 at 15:35











            • yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

              – branquito
              Mar 21 '14 at 15:42











            • maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

              – branquito
              Mar 21 '14 at 15:53











            • Please show the contents of $line -- do it in your question for proper formatting.

              – glenn jackman
              Mar 21 '14 at 15:57
















            This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

            – branquito
            Mar 21 '14 at 15:30





            This is exactly what solves this in a way I wanted (1st example), because it keeps the semantics, which was my goal. Thanks.

            – branquito
            Mar 21 '14 at 15:30




            1




            1





            I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

            – glenn jackman
            Mar 21 '14 at 15:35





            I didn't note the removal of the BEGIN block: an unassigned variable is treated as 0 in a numeric context or the empty string otherwise. So, an unassigned variable will be false in if (p) ...

            – glenn jackman
            Mar 21 '14 at 15:35













            yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

            – branquito
            Mar 21 '14 at 15:42





            yes I noticed, it needs to be set on BEGIN block to zero each time, as it serves as a switch. But interestingly I tried now script using $0 ~ pattern, and it does not work, however with /'"$1"'/ it does work!? :O

            – branquito
            Mar 21 '14 at 15:42













            maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

            – branquito
            Mar 21 '14 at 15:53





            maybe it has something to do with the way $line is retrieved, pattern search is done on the output of whois $line, $line coming from file in a WHILE DO block.

            – branquito
            Mar 21 '14 at 15:53













            Please show the contents of $line -- do it in your question for proper formatting.

            – glenn jackman
            Mar 21 '14 at 15:57





            Please show the contents of $line -- do it in your question for proper formatting.

            – glenn jackman
            Mar 21 '14 at 15:57













            16














            awk -v pattern="$1" '$0 ~ pattern'


            Has an issue in that awk expands the ANSI C escape sequences (like n for newline, f for form feed, \ for backslash and so on) in $1. So it becomes an issue if $1 contains backslash characters which is common in regular expressions. Another approach that doesn't suffer from that issue is to write it:



            PATTERN=$1 awk '$0 ~ ENVIRON["PATTERN"]'


            How bad it's going to be will depend on the awk implementation.



            $ nawk -v 'a=.' 'BEGIN print a'
            .
            $ mawk -v 'a=.' 'BEGIN print a'
            .
            $ gawk -v 'a=.' 'BEGIN print a'
            gawk: warning: escape sequence `.' treated as plain `.'
            .


            All awks work the same for valid escape sequences though:



            $ a='\-b' awk 'BEGIN print ENVIRON["a"]' | od -tc
            0000000 - b n
            0000006


            (content of $a passed as-is)



            $ awk -v a='\-b' 'BEGIN print a' | od -tc
            0000000 - b n
            0000004


            (\ changed to and b changed to a backspace character).






            share|improve this answer

























            • So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

              – branquito
              Mar 21 '14 at 16:24






            • 2





              for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

              – Stéphane Chazelas
              Mar 21 '14 at 16:30












            • it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

              – branquito
              Mar 21 '14 at 16:34







            • 1





              Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

              – Stéphane Chazelas
              Mar 21 '14 at 17:03






            • 1





              Because you need to export a shell variable for it to be passed in the environment to a command.

              – Stéphane Chazelas
              Mar 21 '14 at 17:20















            16














            awk -v pattern="$1" '$0 ~ pattern'


            Has an issue in that awk expands the ANSI C escape sequences (like n for newline, f for form feed, \ for backslash and so on) in $1. So it becomes an issue if $1 contains backslash characters which is common in regular expressions. Another approach that doesn't suffer from that issue is to write it:



            PATTERN=$1 awk '$0 ~ ENVIRON["PATTERN"]'


            How bad it's going to be will depend on the awk implementation.



            $ nawk -v 'a=.' 'BEGIN print a'
            .
            $ mawk -v 'a=.' 'BEGIN print a'
            .
            $ gawk -v 'a=.' 'BEGIN print a'
            gawk: warning: escape sequence `.' treated as plain `.'
            .


            All awks work the same for valid escape sequences though:



            $ a='\-b' awk 'BEGIN print ENVIRON["a"]' | od -tc
            0000000 - b n
            0000006


            (content of $a passed as-is)



            $ awk -v a='\-b' 'BEGIN print a' | od -tc
            0000000 - b n
            0000004


            (\ changed to and b changed to a backspace character).






            share|improve this answer

























            • So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

              – branquito
              Mar 21 '14 at 16:24






            • 2





              for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

              – Stéphane Chazelas
              Mar 21 '14 at 16:30












            • it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

              – branquito
              Mar 21 '14 at 16:34







            • 1





              Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

              – Stéphane Chazelas
              Mar 21 '14 at 17:03






            • 1





              Because you need to export a shell variable for it to be passed in the environment to a command.

              – Stéphane Chazelas
              Mar 21 '14 at 17:20













            16












            16








            16







            awk -v pattern="$1" '$0 ~ pattern'


            Has an issue in that awk expands the ANSI C escape sequences (like n for newline, f for form feed, \ for backslash and so on) in $1. So it becomes an issue if $1 contains backslash characters which is common in regular expressions. Another approach that doesn't suffer from that issue is to write it:



            PATTERN=$1 awk '$0 ~ ENVIRON["PATTERN"]'


            How bad it's going to be will depend on the awk implementation.



            $ nawk -v 'a=.' 'BEGIN print a'
            .
            $ mawk -v 'a=.' 'BEGIN print a'
            .
            $ gawk -v 'a=.' 'BEGIN print a'
            gawk: warning: escape sequence `.' treated as plain `.'
            .


            All awks work the same for valid escape sequences though:



            $ a='\-b' awk 'BEGIN print ENVIRON["a"]' | od -tc
            0000000 - b n
            0000006


            (content of $a passed as-is)



            $ awk -v a='\-b' 'BEGIN print a' | od -tc
            0000000 - b n
            0000004


            (\ changed to and b changed to a backspace character).






            share|improve this answer















            awk -v pattern="$1" '$0 ~ pattern'


            Has an issue in that awk expands the ANSI C escape sequences (like n for newline, f for form feed, \ for backslash and so on) in $1. So it becomes an issue if $1 contains backslash characters which is common in regular expressions. Another approach that doesn't suffer from that issue is to write it:



            PATTERN=$1 awk '$0 ~ ENVIRON["PATTERN"]'


            How bad it's going to be will depend on the awk implementation.



            $ nawk -v 'a=.' 'BEGIN print a'
            .
            $ mawk -v 'a=.' 'BEGIN print a'
            .
            $ gawk -v 'a=.' 'BEGIN print a'
            gawk: warning: escape sequence `.' treated as plain `.'
            .


            All awks work the same for valid escape sequences though:



            $ a='\-b' awk 'BEGIN print ENVIRON["a"]' | od -tc
            0000000 - b n
            0000006


            (content of $a passed as-is)



            $ awk -v a='\-b' 'BEGIN print a' | od -tc
            0000000 - b n
            0000004


            (\ changed to and b changed to a backspace character).







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited yesterday

























            answered Mar 21 '14 at 16:16









            Stéphane ChazelasStéphane Chazelas

            311k57586945




            311k57586945












            • So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

              – branquito
              Mar 21 '14 at 16:24






            • 2





              for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

              – Stéphane Chazelas
              Mar 21 '14 at 16:30












            • it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

              – branquito
              Mar 21 '14 at 16:34







            • 1





              Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

              – Stéphane Chazelas
              Mar 21 '14 at 17:03






            • 1





              Because you need to export a shell variable for it to be passed in the environment to a command.

              – Stéphane Chazelas
              Mar 21 '14 at 17:20

















            • So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

              – branquito
              Mar 21 '14 at 16:24






            • 2





              for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

              – Stéphane Chazelas
              Mar 21 '14 at 16:30












            • it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

              – branquito
              Mar 21 '14 at 16:34







            • 1





              Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

              – Stéphane Chazelas
              Mar 21 '14 at 17:03






            • 1





              Because you need to export a shell variable for it to be passed in the environment to a command.

              – Stéphane Chazelas
              Mar 21 '14 at 17:20
















            So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

            – branquito
            Mar 21 '14 at 16:24





            So you are saying that if pattern was for example d3 to find three digits, that wouldn't work as expected, if I understood you well?

            – branquito
            Mar 21 '14 at 16:24




            2




            2





            for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

            – Stéphane Chazelas
            Mar 21 '14 at 16:30






            for d which is not a valid C escape sequence, that depends on your awk implementation (run awk -v 'a=d3' 'BEGINprint a' to check). But for ` or b, yes definitely. (BTW, I don't know of any awk implementations that understands d` as meaning a digit).

            – Stéphane Chazelas
            Mar 21 '14 at 16:30














            it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

            – branquito
            Mar 21 '14 at 16:34






            it says: awk warning - escape sequence d' treated as plain d' d3, so I guess I would have a problem in this case?

            – branquito
            Mar 21 '14 at 16:34





            1




            1





            Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

            – Stéphane Chazelas
            Mar 21 '14 at 17:03





            Sorry, my bad, I had a typo in my answer. The name of then environment variable has to match ENVIRON["PATTERN"] for the PATTERN environment variable. If you want to use a shell variable, you need to export it first (export variable) or use the ENV=VALUE awk '...ENVIRON["ENV"]' env-var passing syntax as in my answer.

            – Stéphane Chazelas
            Mar 21 '14 at 17:03




            1




            1





            Because you need to export a shell variable for it to be passed in the environment to a command.

            – Stéphane Chazelas
            Mar 21 '14 at 17:20





            Because you need to export a shell variable for it to be passed in the environment to a command.

            – Stéphane Chazelas
            Mar 21 '14 at 17:20











            5














            Try something like:



            awk -v l="$line" -v search="$pattern" 'BEGIN p=0; if ( match( $0, search )) p=1; END if(p) print l >> "outfile.txt" '





            share|improve this answer























            • If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

              – branquito
              Mar 21 '14 at 15:22






            • 1





              The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

              – Hunter Eidson
              Mar 21 '14 at 15:24















            5














            Try something like:



            awk -v l="$line" -v search="$pattern" 'BEGIN p=0; if ( match( $0, search )) p=1; END if(p) print l >> "outfile.txt" '





            share|improve this answer























            • If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

              – branquito
              Mar 21 '14 at 15:22






            • 1





              The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

              – Hunter Eidson
              Mar 21 '14 at 15:24













            5












            5








            5







            Try something like:



            awk -v l="$line" -v search="$pattern" 'BEGIN p=0; if ( match( $0, search )) p=1; END if(p) print l >> "outfile.txt" '





            share|improve this answer













            Try something like:



            awk -v l="$line" -v search="$pattern" 'BEGIN p=0; if ( match( $0, search )) p=1; END if(p) print l >> "outfile.txt" '






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 21 '14 at 15:15









            Hunter EidsonHunter Eidson

            17116




            17116












            • If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

              – branquito
              Mar 21 '14 at 15:22






            • 1





              The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

              – Hunter Eidson
              Mar 21 '14 at 15:24

















            • If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

              – branquito
              Mar 21 '14 at 15:22






            • 1





              The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

              – Hunter Eidson
              Mar 21 '14 at 15:24
















            If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

            – branquito
            Mar 21 '14 at 15:22





            If this behaves same as /regex/ in terms of finding pattern, this could be a nice solution. I will try.

            – branquito
            Mar 21 '14 at 15:22




            1




            1





            The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

            – Hunter Eidson
            Mar 21 '14 at 15:24





            The quick tests I ran seemed to work the same, but I won't even begin to guarantee it... :)

            – Hunter Eidson
            Mar 21 '14 at 15:24











            0














            No, but you can simply interpolate the pattern into the double-quoted string you pass to awk:



            awk -v l="$line" "BEGIN p=0; /$pattern/ p=1; END if(p) print l >> "outfile.txt" "


            Note that you now have to escape the double-quoted awk literal, but it is still the simplest way of accomplishing this.






            share|improve this answer























            • Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

              – branquito
              Mar 21 '14 at 15:14






            • 2





              Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

              – Kilian Foth
              Mar 21 '14 at 15:26






            • 4





              But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

              – Stéphane Chazelas
              Mar 21 '14 at 16:17











            • is that downside of this approach only, having all wrapped in "" ?

              – branquito
              Mar 21 '14 at 16:27















            0














            No, but you can simply interpolate the pattern into the double-quoted string you pass to awk:



            awk -v l="$line" "BEGIN p=0; /$pattern/ p=1; END if(p) print l >> "outfile.txt" "


            Note that you now have to escape the double-quoted awk literal, but it is still the simplest way of accomplishing this.






            share|improve this answer























            • Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

              – branquito
              Mar 21 '14 at 15:14






            • 2





              Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

              – Kilian Foth
              Mar 21 '14 at 15:26






            • 4





              But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

              – Stéphane Chazelas
              Mar 21 '14 at 16:17











            • is that downside of this approach only, having all wrapped in "" ?

              – branquito
              Mar 21 '14 at 16:27













            0












            0








            0







            No, but you can simply interpolate the pattern into the double-quoted string you pass to awk:



            awk -v l="$line" "BEGIN p=0; /$pattern/ p=1; END if(p) print l >> "outfile.txt" "


            Note that you now have to escape the double-quoted awk literal, but it is still the simplest way of accomplishing this.






            share|improve this answer













            No, but you can simply interpolate the pattern into the double-quoted string you pass to awk:



            awk -v l="$line" "BEGIN p=0; /$pattern/ p=1; END if(p) print l >> "outfile.txt" "


            Note that you now have to escape the double-quoted awk literal, but it is still the simplest way of accomplishing this.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 21 '14 at 15:11









            Kilian FothKilian Foth

            680315




            680315












            • Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

              – branquito
              Mar 21 '14 at 15:14






            • 2





              Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

              – Kilian Foth
              Mar 21 '14 at 15:26






            • 4





              But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

              – Stéphane Chazelas
              Mar 21 '14 at 16:17











            • is that downside of this approach only, having all wrapped in "" ?

              – branquito
              Mar 21 '14 at 16:27

















            • Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

              – branquito
              Mar 21 '14 at 15:14






            • 2





              Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

              – Kilian Foth
              Mar 21 '14 at 15:26






            • 4





              But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

              – Stéphane Chazelas
              Mar 21 '14 at 16:17











            • is that downside of this approach only, having all wrapped in "" ?

              – branquito
              Mar 21 '14 at 16:27
















            Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

            – branquito
            Mar 21 '14 at 15:14





            Is this way safe if $pattern contains spaces, my example from above will work as $1 is protected with "$1" double quotes, however not shure what happens in your case.

            – branquito
            Mar 21 '14 at 15:14




            2




            2





            Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

            – Kilian Foth
            Mar 21 '14 at 15:26





            Your original example ends the single-quoted string at the second ', then protects the $1 via double quotes and then tacks another single-quoted string for the second half of the awk program. If I understand correctly, this should have exactly the same effect as protecting the $1 via the outer single quotes - awk never sees the double quotes that you put around it.

            – Kilian Foth
            Mar 21 '14 at 15:26




            4




            4





            But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

            – Stéphane Chazelas
            Mar 21 '14 at 16:17





            But if $pattern contains ^/ system("rm -rf /");, then you're in big trouble.

            – Stéphane Chazelas
            Mar 21 '14 at 16:17













            is that downside of this approach only, having all wrapped in "" ?

            – branquito
            Mar 21 '14 at 16:27





            is that downside of this approach only, having all wrapped in "" ?

            – branquito
            Mar 21 '14 at 16:27











            -3














            You could use the eval function which resolves in this example the nets variable before the awk is run.



            nets="searchtext"
            eval "awk '/"$nets"/'" file.txt





            share|improve this answer





























              -3














              You could use the eval function which resolves in this example the nets variable before the awk is run.



              nets="searchtext"
              eval "awk '/"$nets"/'" file.txt





              share|improve this answer



























                -3












                -3








                -3







                You could use the eval function which resolves in this example the nets variable before the awk is run.



                nets="searchtext"
                eval "awk '/"$nets"/'" file.txt





                share|improve this answer















                You could use the eval function which resolves in this example the nets variable before the awk is run.



                nets="searchtext"
                eval "awk '/"$nets"/'" file.txt






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Feb 21 '17 at 11:51









                Noxy

                32




                32










                answered Feb 21 '17 at 11:19









                NoxyNoxy

                1




                1



























                    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%2f120788%2fpass-shell-variable-as-a-pattern-to-awk%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