Timeline for how to pipe the output of cut to the foreach command?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2014 at 10:22 | history | migrated | from serverfault.com (revisions) | ||
| Apr 15, 2014 at 20:41 | comment | added | Ramy | @Basil, I think that would get too busy and easy to miss in the output. | |
| Apr 15, 2014 at 20:40 | comment | added | Ramy | like this, @Sobrique: grep $(echo ${i} | cut -f1) /tmp/10218.before > /dev/null 2>&1 ? | |
| Apr 15, 2014 at 20:33 | comment | added | Basil | You could have it echo -n "$i: " before the grep, and that would show you visually whether anything you're looping through from .after is missing in .before. | |
| Apr 15, 2014 at 20:28 | comment | added | Sobrique | redirect the grep to /dev/null, and then test $?. | |
| Apr 15, 2014 at 20:25 | comment | added | Ramy | this is correct. Can I trouble you to tell me how to negate the grep. i.e. print a message (or something) when the grep fails. IOW I want to know if any of the words are NOT in the .before file. | |
| Apr 15, 2014 at 20:23 | history | answered | Zypher | CC BY-SA 3.0 |