For loop not working












1















I'm creating a bash script that among other things, checks a list against another list.
Basicly, I created this for loop to check the file "data.txt" for every item in "names.txt" And all matches should be output to "confirmed.txt" which, when finished, should be shown on screen. But for some reason, the file is always blank, am i missing somthing?



test



for code in data.txt 
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt









share|improve this question























  • If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

    – steeldriver
    Jan 6 at 21:59
















1















I'm creating a bash script that among other things, checks a list against another list.
Basicly, I created this for loop to check the file "data.txt" for every item in "names.txt" And all matches should be output to "confirmed.txt" which, when finished, should be shown on screen. But for some reason, the file is always blank, am i missing somthing?



test



for code in data.txt 
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt









share|improve this question























  • If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

    – steeldriver
    Jan 6 at 21:59














1












1








1








I'm creating a bash script that among other things, checks a list against another list.
Basicly, I created this for loop to check the file "data.txt" for every item in "names.txt" And all matches should be output to "confirmed.txt" which, when finished, should be shown on screen. But for some reason, the file is always blank, am i missing somthing?



test



for code in data.txt 
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt









share|improve this question














I'm creating a bash script that among other things, checks a list against another list.
Basicly, I created this for loop to check the file "data.txt" for every item in "names.txt" And all matches should be output to "confirmed.txt" which, when finished, should be shown on screen. But for some reason, the file is always blank, am i missing somthing?



test



for code in data.txt 
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt






command-line bash scripts loop-device






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 6 at 20:13









Tech_PersonTech_Person

298




298













  • If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

    – steeldriver
    Jan 6 at 21:59



















  • If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

    – steeldriver
    Jan 6 at 21:59

















If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

– steeldriver
Jan 6 at 21:59





If the items in data.txt are one-per-line, then you can skip the loop altogether and use grep -f data.txt names.txt or grep -Ff data.txt names.txt if you want them to be treated as fixed strings rather than basic regular expressions. (There's also no need to redirect the matching lines to a file that you're only going to cat once and then delete.)

– steeldriver
Jan 6 at 21:59










1 Answer
1






active

oldest

votes


















2














for code in `cat data.txt`
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt





share|improve this answer
























  • I'm unsure why this worked and my set didn't, but thank you

    – Tech_Person
    Jan 6 at 20:26











  • for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

    – Vijay
    Jan 6 at 20:46













  • ok, Thankyou @Vijay

    – Tech_Person
    Jan 6 at 23:29











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1107512%2ffor-loop-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














for code in `cat data.txt`
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt





share|improve this answer
























  • I'm unsure why this worked and my set didn't, but thank you

    – Tech_Person
    Jan 6 at 20:26











  • for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

    – Vijay
    Jan 6 at 20:46













  • ok, Thankyou @Vijay

    – Tech_Person
    Jan 6 at 23:29
















2














for code in `cat data.txt`
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt





share|improve this answer
























  • I'm unsure why this worked and my set didn't, but thank you

    – Tech_Person
    Jan 6 at 20:26











  • for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

    – Vijay
    Jan 6 at 20:46













  • ok, Thankyou @Vijay

    – Tech_Person
    Jan 6 at 23:29














2












2








2







for code in `cat data.txt`
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt





share|improve this answer













for code in `cat data.txt`
do
grep $code names.txt >> confirmed.txt
done
cat confirmed.txt
rm confirmed.txt






share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 6 at 20:23









VijayVijay

1,5811618




1,5811618













  • I'm unsure why this worked and my set didn't, but thank you

    – Tech_Person
    Jan 6 at 20:26











  • for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

    – Vijay
    Jan 6 at 20:46













  • ok, Thankyou @Vijay

    – Tech_Person
    Jan 6 at 23:29



















  • I'm unsure why this worked and my set didn't, but thank you

    – Tech_Person
    Jan 6 at 20:26











  • for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

    – Vijay
    Jan 6 at 20:46













  • ok, Thankyou @Vijay

    – Tech_Person
    Jan 6 at 23:29

















I'm unsure why this worked and my set didn't, but thank you

– Tech_Person
Jan 6 at 20:26





I'm unsure why this worked and my set didn't, but thank you

– Tech_Person
Jan 6 at 20:26













for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

– Vijay
Jan 6 at 20:46







for code in data.txt, $code is data.txt. Because for does not read the file data.txt. data.txt is just a word/string. `cat data.txt` makes it read the file.

– Vijay
Jan 6 at 20:46















ok, Thankyou @Vijay

– Tech_Person
Jan 6 at 23:29





ok, Thankyou @Vijay

– Tech_Person
Jan 6 at 23:29


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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%2faskubuntu.com%2fquestions%2f1107512%2ffor-loop-not-working%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

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

File:DeusFollowingSea.jpg