From: Justin Rio (c616077@showme.missouri.edu)
Date: 02/05/97

Please. Stop, I beg of you, please stop.
Look, normally I can subject my messages with [NEWBIE][CODE], too.  But
you've been on this list a while, and I've seen several references to grep
just recently.  Grep is a Unix command where the first arguement is a
string of characters you wish to search for. The second is the file(s) you
wish to search.  I'll tell you what has been told to me a thousand times:
"Go buy a C book."  A unix book isn't too bad either.  Before I found the
nifty class.doc at the ftp site, I went into my src directory, and typed
in this: "grep WARRIOR * > warrior.loc"  This search all the src files for
accurances of "WARRIOR", and then put the output into a file named
warrior.loc(ations) so I could brouse it and see it over and over again
without having to occupy a window just with that.  As I went through the
reference, I could erase them from warrior.loc if I deserned(sp) that they
weren't what I was looking for or I adjusted what I needed to do.  
This is also a wonderful way to get an idea of where all the commands are

This post is not just intended for Shaw J (hope I got the name right,
don't have it in front of me), any new coder like us can use this
information.  Any time you want to change something, just search the src
files and maybe autorun for occurances of however the code refers to it.
Then, if you don't understand what you see, by all means post away.  I
think this command, however, can and should be treated like a RTFM or RTFF
topic.  Use it first, then ask.


| Ensure that you have read the CircleMUD Mailing List FAQ: |
|   http://cspo.queensu.ca/~fletcher/Circle/list_faq.html   |

This archive was generated by hypermail 2b30 : 12/18/00 PST