Geary does not quit / stays running in the background
When I close the main Geary window, the Geary process usually does not exit, at least not right away. And so I often open a terminal window and run 'pkill geary'.
Why do I care about whether the process exits or not? Well, from a system design standpoint I much prefer that processes don't hang around when their applications have been closed. But from a more practical perspective, I often want to restart Geary to get back to a clean state after some bug has occurred. For example, at this moment the unread message count is wrong (#364 (closed)), so I want to restart to make it right again. At other times Geary gets into a mode where messages are stuck in the outbox (#625 (closed)), and so I need to restart it. Of course we should fix these bugs, but practically speaking there may always be some bugs like this. I think the user should be able to close and relaunch the application to get back to a clean state without having to run pkill.
Is it a design choice that the process does not exit? Or is it supposed to exit, but some bug is preventing it from doing so? If it is a design choice, I'd be happy to have a DConf key that enables an option to exit immediately.