Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!tinman.cis.ohio-state.edu!bob
From: bob@tinman.cis.ohio-state.edu (Bob Sutterfield)
Newsgroups: gnu.emacs.bug
Subject: Re: grep-command in compile.el
Message-ID: <BOB.89Feb17171451@tinman.cis.ohio-state.edu>
Date: 17 Feb 89 22:14:51 GMT
References: <GRUNWALD.89Feb16134218@flute.cs.uiuc.edu> <TALE.89Feb16214535@consult1.its.rpi.edu>
Sender: news@tut.cis.ohio-state.edu
Distribution: gnu
Organization: The Ohio State University Dept of Computer & Information Science
Lines: 12
In-reply-to: tale@its.rpi.edu's message of 17 Feb 89 02:45:36 GMT

In article <TALE.89Feb16214535@consult1.its.rpi.edu> tale@its.rpi.edu (David C Lawrence) writes:
   In article <GRUNWALD.89Feb16134218@flute.cs.uiuc.edu>  grunwald@flute.cs.uiuc.edu (Dirk Grunwald) writes:
      I just installed gnu grep, and had to name it ``gnugrep'' for
      various reasons.
   For the benefit of those of us who might encounter similar reasons,
   why?

I name every GNU tool something with a "g" in front, particularly if
it otherwise has the same name as a tool that already exists on the
system (e.g. gmake, ggrep).  That's so the people who have
/usr/local/bin in their $PATH before /usr/bin and /bin and all the
rest still get the GNU tools only if they expect to get them.