In simonmichael/hledger#226, if server startup fails, eg because of the port being in use, I don't want to show users a useless browser window.

I think we could propagate exceptions from the forked server thread back to the parent, which would prevent the launch. And/or, we could expose the monitored server starting and the cross-platform browser launching as separate features, allowing more control.