For about as long as I’ve been able to spell “bash”, I’ve seen the debates on the ‘Net about the proper way to use the shell to loop through a text file line-by-line (rather than item-by-item).<\/p>\n
Of the small handful of common methods, it often comes down to this:<\/p>\n
Using Cat<\/strong> Using Redirection<\/strong> So Which Way?<\/strong> Between the two methods I describe above, it’s often said that the Conversely, the redirected method is much more efficient (since you aren’t executing Both points are kinda’ true.\u00a0 But when it comes down to it, the redirected method is just not that hard to understand, and I almost always use\u00a0 it…<\/p>\n Sometimes, Joel…<\/strong> Take this example; I have a few files with a path in one of the fields that is to be parsed, like this:<\/p>\n …and I want to read in the contents of all the few files into the one loop with an Using the standard redirection method in this case, the backslash is interpreted as an “escape”, and is parsed and dropped.\u00a0 Since it’s a filesystem path, I obviously need that backslash; so the way I solved this situation was to use cat, and for each time I encountered the backslash, pass it to Here’s how I did that:<\/p>\n Of course, you notice that the backslash even has to be escaped in the I know, I know what you’re thinking…\u00a0 Just use Perl…
\nWith this method, you call cat<\/code> to pipe the contents of the file into the while<\/code> loop.<\/p>\ncat $inputFile | while read loopLine\r\ndo\r\n (some stuff)\r\ndone<\/pre>\n
\nWith this method, you are redirecting the file into the loop, as indicated by the redirection arrow to the done<\/code> statement in last line.<\/p>\nwhile read loopLine\r\ndo\r\n (some stuff)\r\ndone < $inputFile<\/pre>\n
\nOnce you talk the purists down off the ledge about you not using the IFS variable, and they get over the fact that you aren’t awk<\/code> in the first place, you can move on to the discussion regarding which while read<\/code> approach you’ll use; since most people do it that way anyway, and it’s easier to understand.\u00a0 There.\u00a0 I said it.<\/p>\ncat<\/code> method is “wasteful”, but easier to understand for the person who comes after you. This is apparently because you see right away — as you read through the code in order — the thing that is getting passed into the loop, rather than having wonder or look for it.<\/p>\ncat<\/code>), but someone might not easily understand how it’s happening since they have to scroll down to see the input file , or may not understand what is being looped.<\/p>\n
\n…except in on situation, which is why I write this post; and this is almost always never mentioned in the argue-posts I read on this:\u00a0 What if you need to manipulate the content *before<\/em>* is gets parsed by the while read loop?\u00a0 For instance, backslashes in the line, newlines in the wrong place, etc., read in from a group of files.<\/p>\nservername volumename folder1\\folder2<\/pre>\n
ls<\/code> and a wildcard.<\/p>\nsed<\/code> to add a second backslash as an escape before it gets parsed by the shell while read<\/code> loop.<\/p>\nfor inputfile in `ls $fewFiles`\r\ndo\r\n cat $inputfile | sed -e s\/'\\\\'\/'\\\\\\\\'\/g | while read loopLine\r\n do\r\n # Then I grab the foldername from the short parent path\r\n item=`echo $line |awk -F '\\' '{ print $2 }'`\r\n (some stuff)\r\n done\r\ndone<\/pre>\nsed<\/code> command, as with the double-backslash that I use to replace it…<\/p>\n
\n\ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"