🚀 go-pugleaf

I've recently started using "mkid" for some things, and I've found that I
am periodically running:

	mkid *.[ch]
	etags *.[ch]

as a pair.  It seems a lot of the functionality of etags might be subsumed
by mkid.  Has anyone looked at using mkid as the database for etags instead
of the current TAGS files?  For a single directory (as above), having two
different files isn't that big a deal, but what about using a mkid database
for a whole source tree in order to jump to the definitions of functions
defined anywhere in the tree?

--
=============================================================================
     Fred Douglis, Vrije Universiteit, douglis@cs.vu.nl +31 20 548-5777
=============================================================================