Things to do:

1. Unify all code under the Import/Export/Local/Global macro conventions.
   Finish up the INTERFACE programmer's spec. Decide what to do for
   general error aborts. We need some sort of macro or function call
   for going "PUKE" at any point, but it should also print out meaningful
   information about where it died, which is more difficult. Hmmm. There
   are a number of ways of handling this.

2. Pull all macro/type definitions out of the parser/canvas code that need to
   be known more globally (z.b. the "what" field to parse_adjust) and
   stick in the include/ directory.

3. Make sure that all OS dep. includes are moved into os.h. All code should
   simply rely on os.h to do the interface work, if at all possible (I don't
   see why not).

4. Make sure that all the resource naming conventions are clarified for the
   various parts of emu, i.e., everyone is going to want some part of the
   namespace after "emu and Emu" for their own use. For now, the name
   of the package itself will probably suffice.

5. Make a search for all the XXX commented sections of code and make sure
   the issues raised are resolved.

6. Write some simple shell scripts (or perl, or C, I don't give a shit) for
   opening, editing, tracking and closing out bug reports. If we don't keep
   track of open bugs and/or needed features and try to nail them quickly,
   things will get out of hand pretty fast.

7. Decide on command line arguments to emu. For now, this is just
   -e. We may want to decide on more compatability with the existing xterm
   to make life easier for the users.
