Consider logging configuration

[JonRoma]

As currently released, the alpha version of this software maintains a session log.

This log is not located anywhere that's obvious to the end user, and will eventually grow in size.

Should the default behavior be to suppress logging? This could be developed with or without a global per-system configuration. (See #3.) My instinct tells me that debugging is the principal use case for logging, so logging probably doesn't make sense as the default.

[edthedev]

Moving this in with the planned error message work, as logging and error messaging share a concern with getting messages to users in an intentional way.

I tend to agree we probably want to not keep a local log file unless requested through configuration or a command line flag. Better to ensure any important messages get raised on the console directly to the active user.