sed & awk, 2nd edition by Dale Dougherty and Arnold Robbins Unconfirmed error reports are from readers. They have not yet been approved or disproved by the author or editor and represent solely the opinion of the reader. This page was updated March 13, 2007. Here's a key to the markup: [page-number]: serious technical mistake {page-number}: minor technical mistake : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification UNCONFIRMED errors and suggestions for readers: (24) the bystates program script, has a "$*." to read from standard input, I think this is not needed. {24} 24, 25; on page 24 the following code omits a critical line ---------------------------------------------------- #!/bin/sh awk -F, '{ print $4 ", " $0 }' $* | sort | awk -F, ' $1 == LastState { print "\t" $2 } $1 != LastState { LastState = $1 print $1 }' -------------------------------------------------------- on page 25 the correct piece of code is shown $1 == LastState { print "\t" $2 } $1 != LastState { LastState = $1 print $1 print "\t" $2 }' [242] after 3rd paragraph, in man.split script; If I understand the code correctly, the first comment "#this conditional collects lines until we get to a filename" is clear and accurate for the if portion of the statement, if (file==0) line[++i] = $0 but it is not clear and accurate for the else portion of the statement else print $0 > filename . The else portion of the statement will print out all the lines after the line containing the previous filename until a line with a new filename is identified. The else portion also allows all the lines after the final name to be printed out. This is not clear in the comment of the code, nor is it explained in the description following the code on page 243. I think it would help the readers if the comment was modified and the action of the else statement added to the code description. [300] 3rd paragraph - output of "input.idx" script in middle of page; The contents of the "test" file is shown to include an entry: toolkit (See X Window System). The output of the "input.idx" script does not include the results of processing this entry. From the script, I think the entry should be processed to read: toolkit:(See X Window System)