Bash - Looping through Array in Nested [FOR, WHILE, IF] statements Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionWhy is using a shell loop to process text considered bad practice?How do I test if an item is in a bash array?How to name a file in the deepest level of a directory treeBash: Looping through a stringBASH: looping through lsBash script for looping through filesload bash comands from file one per line and execute them for each file in a directoryBASH attempting to leave nested statements/loops/functionsLooping through lines in several files (bash)Bash - Looping through nested for loop using arraysLooping through an array with for gives different resultsError in Bash Script Nested Conditional Statements

Bonus calculation: Am I making a mountain out of a molehill?

Models of set theory where not every set can be linearly ordered

Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?

How much radiation do nuclear physics experiments expose researchers to nowadays?

What are the motives behind Cersei's orders given to Bronn?

Is the address of a local variable a constexpr?

When to stop saving and start investing?

What is the correct way to use the pinch test for dehydration?

Is the Standard Deduction better than Itemized when both are the same amount?

∞ symbol in external pdf disappears when used as figure

List *all* the tuples!

Is there a "higher Segal conjecture"?

How to motivate offshore teams and trust them to deliver?

Why are there no cargo aircraft with "flying wing" design?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

What does the "x" in "x86" represent?

Is 1 ppb equal to 1 μg/kg?

What would be the ideal power source for a cybernetic eye?

I am not a queen, who am I?

What are the pros and cons of Aerospike nosecones?

Does surprise arrest existing movement?

Why is "Captain Marvel" translated as male in Portugal?

Why was the term "discrete" used in discrete logarithm?

What are 'alternative tunings' of a guitar and why would you use them? Doesn't it make it more difficult to play?



Bash - Looping through Array in Nested [FOR, WHILE, IF] statements



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionWhy is using a shell loop to process text considered bad practice?How do I test if an item is in a bash array?How to name a file in the deepest level of a directory treeBash: Looping through a stringBASH: looping through lsBash script for looping through filesload bash comands from file one per line and execute them for each file in a directoryBASH attempting to leave nested statements/loops/functionsLooping through lines in several files (bash)Bash - Looping through nested for loop using arraysLooping through an array with for gives different resultsError in Bash Script Nested Conditional Statements



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















I am trying to process a large file-set, appending specific lines into the "test_result.txt" file - I achieved it -not very elegantly- with the following code.



for i in *merged; do
while read -r lo; do
if [[ $lo == *"ID"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Instance"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"NOT"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"AI"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Sitting"* ]]; then
echo $lo >> test_result.txt

done < $i
done


However, I am trying to size-it-down using an array - which resulted in quite an unsuccessful attempt.



KEYWORDS=("ID" "Instance" "NOT" "AI" "Sitting" )
KEY_COUNT=0

for i in *merged; do
while read -r lo; do
if [[$lo == $KEYWORDS[@] ]]; then
echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
fi
done < $i
done









share|improve this question









New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 3





    How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

    – steeldriver
    Apr 10 at 10:17






  • 2





    Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

    – Freddy
    Apr 10 at 10:34

















3















I am trying to process a large file-set, appending specific lines into the "test_result.txt" file - I achieved it -not very elegantly- with the following code.



for i in *merged; do
while read -r lo; do
if [[ $lo == *"ID"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Instance"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"NOT"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"AI"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Sitting"* ]]; then
echo $lo >> test_result.txt

done < $i
done


However, I am trying to size-it-down using an array - which resulted in quite an unsuccessful attempt.



KEYWORDS=("ID" "Instance" "NOT" "AI" "Sitting" )
KEY_COUNT=0

for i in *merged; do
while read -r lo; do
if [[$lo == $KEYWORDS[@] ]]; then
echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
fi
done < $i
done









share|improve this question









New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 3





    How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

    – steeldriver
    Apr 10 at 10:17






  • 2





    Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

    – Freddy
    Apr 10 at 10:34













3












3








3








I am trying to process a large file-set, appending specific lines into the "test_result.txt" file - I achieved it -not very elegantly- with the following code.



for i in *merged; do
while read -r lo; do
if [[ $lo == *"ID"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Instance"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"NOT"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"AI"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Sitting"* ]]; then
echo $lo >> test_result.txt

done < $i
done


However, I am trying to size-it-down using an array - which resulted in quite an unsuccessful attempt.



KEYWORDS=("ID" "Instance" "NOT" "AI" "Sitting" )
KEY_COUNT=0

for i in *merged; do
while read -r lo; do
if [[$lo == $KEYWORDS[@] ]]; then
echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
fi
done < $i
done









share|improve this question









New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I am trying to process a large file-set, appending specific lines into the "test_result.txt" file - I achieved it -not very elegantly- with the following code.



for i in *merged; do
while read -r lo; do
if [[ $lo == *"ID"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Instance"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"NOT"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"AI"* ]]; then
echo $lo >> test_result.txt
fi
if [[ $lo == *"Sitting"* ]]; then
echo $lo >> test_result.txt

done < $i
done


However, I am trying to size-it-down using an array - which resulted in quite an unsuccessful attempt.



KEYWORDS=("ID" "Instance" "NOT" "AI" "Sitting" )
KEY_COUNT=0

for i in *merged; do
while read -r lo; do
if [[$lo == $KEYWORDS[@] ]]; then
echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
fi
done < $i
done






bash






share|improve this question









New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Apr 10 at 22:20









Rui F Ribeiro

42.1k1483142




42.1k1483142






New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Apr 10 at 9:52









AF.BJAF.BJ

185




185




New contributor




AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






AF.BJ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 3





    How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

    – steeldriver
    Apr 10 at 10:17






  • 2





    Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

    – Freddy
    Apr 10 at 10:34












  • 3





    How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

    – steeldriver
    Apr 10 at 10:17






  • 2





    Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

    – Freddy
    Apr 10 at 10:34







3




3





How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

– steeldriver
Apr 10 at 10:17





How large is the file set? This sounds like an XY problem that could be better accomplished by a straightforward grep command.

– steeldriver
Apr 10 at 10:17




2




2





Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

– Freddy
Apr 10 at 10:34





Small side note: Instead of KEY_COUNT="`expr $KEY_COUNT + 1`" you could also write ((KEY_COUNT++))

– Freddy
Apr 10 at 10:34










2 Answers
2






active

oldest

votes


















5














It looks like you want to get all the lines that contains at least one out of a set of words, from a set of files.



Assuming that you don't have many thousands of files, you could do that with a single grep command:



grep -wE '(ID|Instance|NOT|AI|Sitting)' ./*merged >outputfile


This would extract the lines matching any of the words listed in the pattern from the files whose names matches *merged.



The -w with grep ensures that the given strings are not matched as substrings (i.e. NOT will not be matched in NOTICE). The -E option enables the alternation with | in the pattern.



Add the -h option to the command if you don't want the names of the files containing matching lines in the output.



If you do have many thousands of files, the above command may fail due to expanding to a too long command line. In that case, you may want to do something like



for file in ./*merged; do
grep -wE '(ID|Instance|NOT|AI|Sitting)' "$file"
done >outputfile


which would run the grep command once on each file, or,



find . -maxdepth 1 -type f -name '*merged' 
-exec grep -wE '(ID|Instance|NOT|AI|Sitting)' + >outputfile


which would do as few invocations of grep as possible with as many files as possible at once.



Related:



  • Why is using a shell loop to process text considered bad practice?





share|improve this answer




















  • 1





    It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

    – AF.BJ
    Apr 10 at 16:45











  • @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

    – muru
    Apr 11 at 1:15


















3














Adding an array doesn't particularly help: you still would need to loop over the elements of the array (see How do I test if an item is in a bash array?):



while read -r lo; do
for keyword in "$keywords[@]"; do
if [[ $lo == *$keyword* ]]; then
echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
fi
done
done < "$i"


It might be better to use a case statement:



while read -r lo; do
case $lo in
*(ID|Instance|NOT|AI|Sitting)*)
echo "$lo" >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
;;
esac
done < "$i"


(I assume you do further processing of these lines within the loop. If not, grep or awk could do this more efficiently.)






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
    );



    );






    AF.BJ is a new contributor. Be nice, and check out our Code of Conduct.









    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511636%2fbash-looping-through-array-in-nested-for-while-if-statements%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    It looks like you want to get all the lines that contains at least one out of a set of words, from a set of files.



    Assuming that you don't have many thousands of files, you could do that with a single grep command:



    grep -wE '(ID|Instance|NOT|AI|Sitting)' ./*merged >outputfile


    This would extract the lines matching any of the words listed in the pattern from the files whose names matches *merged.



    The -w with grep ensures that the given strings are not matched as substrings (i.e. NOT will not be matched in NOTICE). The -E option enables the alternation with | in the pattern.



    Add the -h option to the command if you don't want the names of the files containing matching lines in the output.



    If you do have many thousands of files, the above command may fail due to expanding to a too long command line. In that case, you may want to do something like



    for file in ./*merged; do
    grep -wE '(ID|Instance|NOT|AI|Sitting)' "$file"
    done >outputfile


    which would run the grep command once on each file, or,



    find . -maxdepth 1 -type f -name '*merged' 
    -exec grep -wE '(ID|Instance|NOT|AI|Sitting)' + >outputfile


    which would do as few invocations of grep as possible with as many files as possible at once.



    Related:



    • Why is using a shell loop to process text considered bad practice?





    share|improve this answer




















    • 1





      It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

      – AF.BJ
      Apr 10 at 16:45











    • @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

      – muru
      Apr 11 at 1:15















    5














    It looks like you want to get all the lines that contains at least one out of a set of words, from a set of files.



    Assuming that you don't have many thousands of files, you could do that with a single grep command:



    grep -wE '(ID|Instance|NOT|AI|Sitting)' ./*merged >outputfile


    This would extract the lines matching any of the words listed in the pattern from the files whose names matches *merged.



    The -w with grep ensures that the given strings are not matched as substrings (i.e. NOT will not be matched in NOTICE). The -E option enables the alternation with | in the pattern.



    Add the -h option to the command if you don't want the names of the files containing matching lines in the output.



    If you do have many thousands of files, the above command may fail due to expanding to a too long command line. In that case, you may want to do something like



    for file in ./*merged; do
    grep -wE '(ID|Instance|NOT|AI|Sitting)' "$file"
    done >outputfile


    which would run the grep command once on each file, or,



    find . -maxdepth 1 -type f -name '*merged' 
    -exec grep -wE '(ID|Instance|NOT|AI|Sitting)' + >outputfile


    which would do as few invocations of grep as possible with as many files as possible at once.



    Related:



    • Why is using a shell loop to process text considered bad practice?





    share|improve this answer




















    • 1





      It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

      – AF.BJ
      Apr 10 at 16:45











    • @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

      – muru
      Apr 11 at 1:15













    5












    5








    5







    It looks like you want to get all the lines that contains at least one out of a set of words, from a set of files.



    Assuming that you don't have many thousands of files, you could do that with a single grep command:



    grep -wE '(ID|Instance|NOT|AI|Sitting)' ./*merged >outputfile


    This would extract the lines matching any of the words listed in the pattern from the files whose names matches *merged.



    The -w with grep ensures that the given strings are not matched as substrings (i.e. NOT will not be matched in NOTICE). The -E option enables the alternation with | in the pattern.



    Add the -h option to the command if you don't want the names of the files containing matching lines in the output.



    If you do have many thousands of files, the above command may fail due to expanding to a too long command line. In that case, you may want to do something like



    for file in ./*merged; do
    grep -wE '(ID|Instance|NOT|AI|Sitting)' "$file"
    done >outputfile


    which would run the grep command once on each file, or,



    find . -maxdepth 1 -type f -name '*merged' 
    -exec grep -wE '(ID|Instance|NOT|AI|Sitting)' + >outputfile


    which would do as few invocations of grep as possible with as many files as possible at once.



    Related:



    • Why is using a shell loop to process text considered bad practice?





    share|improve this answer















    It looks like you want to get all the lines that contains at least one out of a set of words, from a set of files.



    Assuming that you don't have many thousands of files, you could do that with a single grep command:



    grep -wE '(ID|Instance|NOT|AI|Sitting)' ./*merged >outputfile


    This would extract the lines matching any of the words listed in the pattern from the files whose names matches *merged.



    The -w with grep ensures that the given strings are not matched as substrings (i.e. NOT will not be matched in NOTICE). The -E option enables the alternation with | in the pattern.



    Add the -h option to the command if you don't want the names of the files containing matching lines in the output.



    If you do have many thousands of files, the above command may fail due to expanding to a too long command line. In that case, you may want to do something like



    for file in ./*merged; do
    grep -wE '(ID|Instance|NOT|AI|Sitting)' "$file"
    done >outputfile


    which would run the grep command once on each file, or,



    find . -maxdepth 1 -type f -name '*merged' 
    -exec grep -wE '(ID|Instance|NOT|AI|Sitting)' + >outputfile


    which would do as few invocations of grep as possible with as many files as possible at once.



    Related:



    • Why is using a shell loop to process text considered bad practice?






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 10 at 14:39

























    answered Apr 10 at 12:54









    KusalanandaKusalananda

    142k18265440




    142k18265440







    • 1





      It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

      – AF.BJ
      Apr 10 at 16:45











    • @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

      – muru
      Apr 11 at 1:15












    • 1





      It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

      – AF.BJ
      Apr 10 at 16:45











    • @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

      – muru
      Apr 11 at 1:15







    1




    1





    It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

    – AF.BJ
    Apr 10 at 16:45





    It is indeed a file-set of a few thousand. Originally, I built other processes into the loop but running grep separately - before the extra tweakings - it's a cleaner solution. Just needed to add the "-h" option to suppress default prefixes - Thnks.

    – AF.BJ
    Apr 10 at 16:45













    @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

    – muru
    Apr 11 at 1:15





    @AF.BJ since this answer solved your problem, consider accepting it: What should I do when someone answers my question?

    – muru
    Apr 11 at 1:15













    3














    Adding an array doesn't particularly help: you still would need to loop over the elements of the array (see How do I test if an item is in a bash array?):



    while read -r lo; do
    for keyword in "$keywords[@]"; do
    if [[ $lo == *$keyword* ]]; then
    echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
    fi
    done
    done < "$i"


    It might be better to use a case statement:



    while read -r lo; do
    case $lo in
    *(ID|Instance|NOT|AI|Sitting)*)
    echo "$lo" >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
    ;;
    esac
    done < "$i"


    (I assume you do further processing of these lines within the loop. If not, grep or awk could do this more efficiently.)






    share|improve this answer



























      3














      Adding an array doesn't particularly help: you still would need to loop over the elements of the array (see How do I test if an item is in a bash array?):



      while read -r lo; do
      for keyword in "$keywords[@]"; do
      if [[ $lo == *$keyword* ]]; then
      echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
      fi
      done
      done < "$i"


      It might be better to use a case statement:



      while read -r lo; do
      case $lo in
      *(ID|Instance|NOT|AI|Sitting)*)
      echo "$lo" >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
      ;;
      esac
      done < "$i"


      (I assume you do further processing of these lines within the loop. If not, grep or awk could do this more efficiently.)






      share|improve this answer

























        3












        3








        3







        Adding an array doesn't particularly help: you still would need to loop over the elements of the array (see How do I test if an item is in a bash array?):



        while read -r lo; do
        for keyword in "$keywords[@]"; do
        if [[ $lo == *$keyword* ]]; then
        echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
        fi
        done
        done < "$i"


        It might be better to use a case statement:



        while read -r lo; do
        case $lo in
        *(ID|Instance|NOT|AI|Sitting)*)
        echo "$lo" >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
        ;;
        esac
        done < "$i"


        (I assume you do further processing of these lines within the loop. If not, grep or awk could do this more efficiently.)






        share|improve this answer













        Adding an array doesn't particularly help: you still would need to loop over the elements of the array (see How do I test if an item is in a bash array?):



        while read -r lo; do
        for keyword in "$keywords[@]"; do
        if [[ $lo == *$keyword* ]]; then
        echo $lo >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
        fi
        done
        done < "$i"


        It might be better to use a case statement:



        while read -r lo; do
        case $lo in
        *(ID|Instance|NOT|AI|Sitting)*)
        echo "$lo" >> ~/Desktop/test_result.txt && KEY_COUNT="`expr $KEY_COUNT + 1`"
        ;;
        esac
        done < "$i"


        (I assume you do further processing of these lines within the loop. If not, grep or awk could do this more efficiently.)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 10 at 10:20









        murumuru

        37.9k590166




        37.9k590166




















            AF.BJ is a new contributor. Be nice, and check out our Code of Conduct.









            draft saved

            draft discarded


















            AF.BJ is a new contributor. Be nice, and check out our Code of Conduct.












            AF.BJ is a new contributor. Be nice, and check out our Code of Conduct.











            AF.BJ is a new contributor. Be nice, and check out our Code of Conduct.














            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%2f511636%2fbash-looping-through-array-in-nested-for-while-if-statements%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

            Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

            Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

            Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020