[Conkeror] effect of can_kill_last_buffer=false

[Jeremy Maitin-Shepard]

"Chengqi(Lars) Song" <songcq at gmail.com> writes:

> hi john,
> do you think it's better to make the effect of
> 	can_kill_last_buffer=false 
> to be can kill last buffer but the conkeror remains open? like some
> other browsers do.

Conkeror is currently designed, like Emacs, under the assumption that
there is always a current buffer (in each window).  For that reason, if
we allowed the last buffer of a window to be killed without deleting the
window itself, an inconsistent state would result.  (Note, for instance,
that the current keymap is determined from the current buffer.)  One
option that has been proposed on bugs.conkeror.org, though, is to open
an about:blank buffer if the last buffer is killed.

-- 
Jeremy Maitin-Shepard