Re: locate/updatedb on crack
> > now with "gimpinitl.h." > > gimpintl.h != gimpinit.h > > > The other found gimp.h, which is in the same dir as gimpinit.h. But > > it still can't locate gimpinitl.h. Well, that's embarassing. Stupid typos... Maybe I'm dyslexic (is that spelled right?, ispell flags it, no suggestions though, and I can't think of anything else)... Yeah, that's it. To partially save face, I confused gimpintl.h with gimpinitl.h, not gimpintl.h and gimpinit.h, although it might not look like that... -- Pat Mahoney <[EMAIL PROTECTED]> I had no shoes and I pitied myself. Then I met a man who had no feet, so I took his shoes. -- Dave Barry
locate/updatedb on crack
Locate has been acting strangely lately, please have a look: I just ran updatedb two minutes ago; updatedb.conf appears below. [EMAIL PROTECTED]:~$ locate /usr/include/libgimp/gimpintl.h /usr/include/libgimp/gimpintl.h # ok, it found it [EMAIL PROTECTED]:~$ locate gimpinit.h # but not this time? [EMAIL PROTECTED]:~$ locate /libgimp/gimpintl.h # good /usr/include/libgimp/gimpintl.h [EMAIL PROTECTED]:~$ locate /gimpintl.h # again /usr/include/libgimp/gimpintl.h [EMAIL PROTECTED]:~$ locate gimpintl.h # ok, now why does it work here? /usr/include/libgimp/gimpintl.h [EMAIL PROTECTED]:~$ locate gimpintl.h # again? /usr/include/libgimp/gimpintl.h I'm using two Eterms. Now it's working in one of them (the one above), but not the other. Both seem to work fine except for the other one now with "gimpinitl.h." The other found gimp.h, which is in the same dir as gimpinit.h. But it still can't locate gimpinitl.h. /etc/updatedb.conf: # This file sets environment variables which are used by updatedb # filesystems which are pruned from updatedb database PRUNEFS="NFS nfs afs proc smbfs autofs auto iso9660 ncpfs coda" export PRUNEFS # paths which are pruned from updatedb database PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /amd /alex /var/spool" export PRUNEPATHS # netpaths which are added NETPATHS="" export NETPATHS ### end of updatedb.conf ## -- Pat Mahoney <[EMAIL PROTECTED]> I cannot overemphasize the importance of good grammar. . What a crock. I could easily overemphasize the importance of good grammar. For example, I could say: "Bad grammar is the leading cause of slow, painful death in North America," or "Without good grammar, the United States would have lost World War II." -- Dave Barry, "An Utterly Absurd Look at Grammar"
