14 Jun 15 13:54, you wrote to me:

 NB>>> cat nodelist.000 | grep 'user_name'

 ml>> grep it directly and save a step plus resources ;)

 NB> I don't care much for saving resources on a 6-core machine with
 NB> hyperthreading and 16gb ram.

me either, really... not on this box with 8 4ghz cores and 16gb RAM...
don't care about that hyperthreading mess, either ;) O:)

 ml>>      grep -Ei -e ",nicholas_boel," fido/nodelist/nodelist.145

 ml>> then one can also get more specific looking in specific fields... for
 ml>> example, i know they're in wisconsin and the node number i'm looking
 ml>> for starts with a '7'...

 ml>>      grep -Ei -e ".*,7.*,.*_wi,nicholas_boel,"
 ml>> fido/nodelist/nodelist.145

 ml>> ,701,Dark_Sorrow,Pewaukee_WI,Nicholas_Boel,-Unpublished-,300,CM,MO,INA
 ml>> :binkp.pharcyde.org,IBN:24555 ,702,Mystic_Test_System,Pewaukee_WI,Nich
 ml>> olas_Boel,-Unpublished-,300,CM,INA:binkp.pharcyde.org,IBN:24556

 NB> More than one way to skin a cat and I went with the easiest, but thanks for
 NB> yet another one-upping. :)

it wasn't one-upping... at least it wasn't intended that way... pure grep
is, actually, the easiest since it doesn't involve any other tools... it is
the easiest in this case when one is just looking for the line in
question... i have some real doozies here that use cut, uniq, sort and a
couple of others feeding and being fed from grep... long arsed command
lines with numerous pipes... i'm glad i saved them to a script ;)

)\/(ark

... Don't do it if you can't keep it up.
---