On Fri, Sep 25, 2009 at 06:48:19AM -0700, Jeremy Maitin-Shepard wrote: > Jesse Luehrs <[email protected]> writes: > > >> From ab6618459e75aa8c940c0cedeb5c1ba5a43b028a Mon Sep 17 00:00:00 2001 > > From: Jesse Luehrs <[email protected]> > > Date: Fri, 25 Sep 2009 02:26:45 -0500 > > Subject: [PATCH] handle killing the last buffer a little better > > > replace it with an empty buffer if we aren't allowed to kill it > > This doesn't seem that useful since the only thing you would do with the > new buffer is use it to browse to a different URL, which you could have > done with the existing buffer anyway.
It's more for consistency - if I tell it to kill a buffer, then I want that buffer to be killed, and whether or not the window closes from killing the last buffer is orthogonal to that. This is also how vimperator handles the situation. > If this is really desirable behavior, though, you could create a user > variable that enables this behavior when set, but leaves the existing > behavior when unset, as I would want the existing behavior to still be > available. I can make it an option, if you think that would be better. -doy _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
