Command precedence in PIRDE is a bit tricky. First there's shell
subroutines. There may be some fake commands in here to serve as reminders
of the existance of shell subroutines such as "setup", which has to happen
in the main shell context to work right, and is therefor a shell
subroutine defined in PIRDErc.  Then there's whatever dir is first in
PATH, which defaults to here.

Commands special to particular types of databases are in subdirectories of
this directory. When you do "setup mail" for example, the ./mail
subdirectory is put at THE FRONT of PATH. This allows the mail-special
commands to actually superceed the generic versions, which can help with
handling differing database types and so on.


