If you're in todo-mode and you type `q' to exit it, and in the buffer
that is now current you invoke quit-window, then the todo-mode buffer
becomes current again.  But it was supposed to have been buried by `q',
so it should not immediately become current again.

This problem is due to a faulty use of bury-buffer in commit ea3ae33b
from 2013-05-16, and it's annoyed me ever since, but I didn't bother to
do anything about it till now.


2017-05-28  Stephen Berman  <stephen.berman@gmx.net>

	Prevent buried todo-mode buffer from being current too soon

	This happened due to commit ea3ae33b from 2013-05-16, which
	prevented quitting todo-mode buffer after visiting
	todo-archive buffer from making the archive buffer current
	again.  Avoid this now by simply killing the archive buffer,
	since there's no need to keep it a live buffer.  Consequently,
	quitting a todo-mode buffer can now use bury-buffer without an
	argument, which ensures that is will not becomes current on
	quitting the next buffer.

	* lisp/calendar/todo-mode.el (todo-quit): Kill todo-archive-mode
	buffer instead of burying it.  This now allows exiting the
	todo-mode buffer with bury-buffer without an argument, so do that.